jemalloc page size issue for arm64

[nephaste]

jemalloc page size issue for arm64

[gauthier-th]

Updating Next.js is on our roadmap, so it might comes in a few days/weeks/months.

[Fallenbagel]

Building on QPKG on QNAP is not officially supported. And this seems to be a nextjs issue (see ajnart/homarr#598 (comment))

And homarr's solution seems to be upgrading to nextjs 13 (where jemalloc page size seems to have been increased for arm64). We are on 12. So until we can update to nextjs 13, there is nothing that can be done.

Docker image is already built so that might work. We recommend using that method.

CC: @gauthier-th

[nephaste]

Many users prefer nativ, than docker for many reasons... the myqnap.org repository propose only undockerised QPKG,
hope you will update nextjs soon ...

Thanks again,

[gauthier-th]

@nephaste the Next.js update should be done. It's not release yet but it's available with the update-nextjs branch or the preview-nextjs-update tag.
Could you please try it and check if it resolves your error?

[nephaste]

Hi @gauthier-th , thanks a lot...

not sure what i did wrong but getting a sharp command not found with the branch

[nephaste]

but seem it can build it via node-gyp

and all is compiled finally

[Fallenbagel]

Hi @gauthier-th , thanks a lot...

not sure what i did wrong but getting a sharp command not found with the branch

That is probably my fault. I added sharp as a dependency and im not sure if I set it up correctly

[gauthier-th]

Hi @gauthier-th , thanks a lot...
not sure what i did wrong but getting a sharp command not found with the branch

That is probably my fault. I added sharp as a dependency and im not sure if I set it up correctly

It might be coming from us as well. When we build it for arm64 on our CI this error doesn't occurs though.
The CI is using Node.js v18.18 and Yarn v1.22.19.

What is your Yarn version? (yarn --version)

[gauthier-th]

I didn't saw it was already written in your screenshot sorry.
Could you try it with Node.js v18 instead of Node.js v20? We don't really support Node.js v20.

[nephaste]

Hi , it is already NodeJS v18 (cant remember the version exactly since it is also cross compiled for current libc)

yarn is installed to latest release as well (on each compilaton from source) just built the Qnap QPKG, and it seems to work as it is

[nephaste]

[gauthier-th]

In the end, did you manage to build it and run it without performing any extra action?

[nephaste]

Exactly... no action I tried to npm install -g sharp in my nodejs directory and also into the jellyseerr directory but the error was still here, but job process continue seems to be build it with node-gyp on my understanding..

[Fallenbagel]

Exactly... no action I tried to npm install -g sharp in my nodejs directory and also into the jellyseerr directory but the error was still here, but job process continue seems to be build it with node-gyp on my understanding..

Could you try now? Remember to use nodejs 20 and pnpm 9

[nephaste]

something changed ? i installed pnpm 9.4.0 in my PATH but getting another error now

[nephaste]

I added npm install -g next to my PATH, seems to compile now

[gauthier-th]

We did quite a lot of updates the last few days. Theses updates includes:

• Update to Next.js v14
• Update to Node.js v20
• Switch from Yarn to pnpm

This means you will have to install pnpm, and install your Node.js dependencies with pnpm instead of Yarn.
You can follow the build instructions in the README which has also been updated.

You shouldn't need to install global packages with npm (actually you should remove theses).

Could you please test it on develop without any extra flags or workarounds?

[nephaste]

Will give a try actually compilation is taking ages :

i need build from source some nodejs module (like sqlite3 because the provided binaries are using an upper libc than the NAS)

[Fallenbagel]

I added npm install -g next to my PATH, seems to compile now

Just a heads up. Look at your build command. You're doing ../bin/yarn run build

We don't support yarn anymore.
And building with yarn is going to cause you issues.

[nephaste]

yes just saw your message... tried pnpm but seems still need install next

and not sure what belong the sqlite3 error message

[Fallenbagel]

yes just saw your message... tried pnpm but seems still need install next

and not sure what belong the sqlite3 error message

You're still running the wrong package.json
It's still yarn building that's why it's broken.

Could you hop onto discord? We'll guide you through this

[nephaste]

Should i use main branch (like on the README )

the current branch i am using now

git clone https://github.com/Fallenbagel/jellyseerr.git && cd jellyseerr
git checkout main

or going back to on update-nextjs branch

[Fallenbagel]

Should i use main branch (like on the README )

the current branch i am using now

git clone https://github.com/Fallenbagel/jellyseerr.git && cd jellyseerr
git checkout main

or going back to on update-nextjs branch

That's your issue.
You should be on develop.
Then run pnpm install --frozen-lockfile
Then pnpm build

[nephaste]

seems to work, but falling into an error i need check my flags and why he does not find some headers

[nephaste]

mmmmmm look like i must ugrpade m libvips version 😢

[nephaste]

updated libvips but still falling in another strange issue ... not sure what is the problem
look like a compatibility issue with sharp