Skip to content
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

Unable to build nodejs-native #743

Closed
paletteguy opened this issue Oct 2, 2023 · 4 comments
Closed

Unable to build nodejs-native #743

paletteguy opened this issue Oct 2, 2023 · 4 comments

Comments

@paletteguy
Copy link

Building nodejs-native on kirkstone and mickledore fails with this error:

build/tmp/hosttools/ld: .//Release/obj.target/tools/v8_gypfiles/libv8_initializers.a: error adding symbols: malformed archive
| collect2: error: ld returned 1 exit status
| rm cd3612620867e7ead4ace8fa0a5fd4e7a74528f5.intermediatemake[1]: *** [tools/v8_gypfiles/mksnapshot.target.mk:198: Release/mksnapshot] Error 1
| a66092d7422de8d53257377725a0e74d1bec44d5.intermediate 8d65583cbda2e9df30d961a1eba822d938bb57dd.intermediate
| make: *** [Makefile:134: node] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.

Build is performed with -j1 to avoid memory issue.

Host: is Ubuntu 22.04 (LinuxThinkPad-P73 5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux)

Building for target arm64 works fine.

@kraj
Copy link
Contributor

kraj commented Oct 4, 2023

malformed archive, means something crashed perhaps during build. Check if build system dumped some cores and what those are. Its required to have 16G minimal RAM for building yocto without problems.

@paletteguy
Copy link
Author

I've got 32 GB of memory 500 GB left on drive and I'm compiling with PARALLEL_MAKE = "-j1" as append to receipe for nodejs

@kraj
Copy link
Contributor

kraj commented Oct 5, 2023

mksnapshot needs a bit of RAM but 32gb should be fine. Can you see if backporting 33c96b7 helps.

@paletteguy
Copy link
Author

Thanks for support.

The root-cause was a homebrew installation causing the linking to malformed. After uninstalling Homebrew I had no issue compiling nodejs-native.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants