-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RISCV64 on Alpine (not on Ubuntu): ../gf16/gf16_rvv_common.h:33:20: error: incompatible type for argument 3 of '__riscv_vxor_vx_i16m1_m' #62
Comments
Dockerfile:
Full docker build output attached |
FWIW: on x86, the same Dockerfile results with success, with parpar working
|
Thanks. Could you try again using the dev branch instead of master? |
build-parpar-riscv64.log But: failure later on:
|
Thanks again. Hmm, can you try searching for and deleting |
OK, so let's put that into the Dockerfile
EDIT: A grep shows PARPAR_LIBDL_SUPPORT is not there anymore in binding.gyp, so the sed is working ... still same error:
|
I don't really know then. Maybe some issue with RVV and LTO? Try replacing the |
I'll try. In the meantime I had already something (likely?) ugly (based on nodejs/node@bec959e) , but still error
|
same error with
|
build_parpar-ubuntu2410-riscv64.log I built from Ubuntu:24.10 (also with gcc-14.2.0, still on RISCV64), and that works. See tail below. With very clean Dockerfile (no specials):
Which binary can I check for rvv commands (with objdump)? I only see .js and . json files, and there must be a binary?
|
Hmm, maybe node-gyp is overriding the CFLAGS.
My guess is it's something with the musl build chain that doesn't like it. I think you previously built this fine on Ubuntu.
The library should be build/Release/parpar_gf.node Your output shows |
Same error. Shall I close this issue as "Alpine specific"?
|
In the Ubuntu build version indeed rvv commands inside Cool
EDIT I could have found it:
Thanks |
I'm willing to diagnose this as long as you're willing to test out my random shots in the dark. I don't really have your environment set up, so it's hard for me to replicate. If you are willing to diagnose further: It's odd that it looks like LTO is being invoked despite attempts to disable it. |
Thank you.
Still my offer to you: via IPv6 access to my riscv system I did stuff, and I'm dumping it here, without thinking about it too much TLDR: it now builds (maybe because of ignoring the returncode in the Dockerfile). EDIT: After a manual Docker build command longer, but nothing special:
Dockerfile now with all precautions, plus ignoring the output of the build
EDIT: the below solved with
Binaries are there
|
Thanks, looks like LTO is still being enabled. Can you try with this Dockerfile instead?
|
That one built without problems. build.Dockerfile.animetosho_2024-08-26.log Still strange: an error when trying to run parpar.js ... which is solved by manuall installing async. Which I tried putting into Dockerfile, without solving it.
Next: building without the hack The grep output:
|
Yay!
Usually the |
Trying to build ParPar in a docker (alpine:edge, gcc 14) on RISCV64, I get the output with errors below
As it's in rvv, I'm assuming it's ParPar specific (not something upstream)?
Is this something in the ParPar source code, or on my side?
The text was updated successfully, but these errors were encountered: