Open vortexilation opened 1 day ago
Hi @vortexilation After applying your own patches to node.js, have you hostbuilt node.js?
make package/feeds/packages/node/host/{clean,compile}
make package/feeds/packages/node/{clean,compile}
@nxhack Yes, of course, the problem is when compiling node-yarn, node/npm segmentation fault.
Thanks for joining in this issue.
(It's just a guess...) Perhaps you should prepare separate host-build and target-build versions of the linking library. You may also need to devise a way to build obj.host and obj.target.
If the target is not x86_64, it seems like you can clearly see where the error is.
(It's just a guess...) Perhaps you should prepare separate host-build and target-build versions of the linking library. You may also need to devise a way to build obj.host and obj.target.
Your suggestion is for protobuf?, can you elaborate more or give an example?.
If the target is not x86_64, it seems like you can clearly see where the error is.
The target is x86_64, just like the build host.
Maintainer: @nxhack Environment: x86_64, glibc
Description:
Posting it in here also.
It seems that node will failed to compile if there is already compiled abseil-cpp in $(STAGING_DIR_HOSTPKG)/lib dir with the following error.
Abseil-cpp was compiled from bundled in protobuf 25.3, here is the draft Makefile :
Node 22.11.0 will able to compile with the following patch :
but will segmentation fault when running npm or compiling node-yarn :