From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15061] New: Node.js Package fails to build against musl i386
Date: Mon, 17 Oct 2022 07:43:39 +0000 [thread overview]
Message-ID: <bug-15061-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15061
Bug ID: 15061
Summary: Node.js Package fails to build against musl i386
Product: buildroot
Version: 2022.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: hello.skyclo@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hello,
I have been trying to build the Nodejs package against musl for a i386 Pentium3
target. Nodejs has an unofficial build for musl (x64) and for x86 (gcc),
however there is no unofficial build for x86 musl. I assume it's possible to
build against musl-i386. I built nodejs against uClibc-ng i386 on the exact
same machine months ago, however now that doesn't work either. For reference,
my system uses glibc x64 and does not contain a musl i386 linker (since Ubuntu
no longer supports i386).
The full output of make is attached here along with the defconfig (for
reprod.):
https://gist.github.com/Skyclo/4168deaa1a73be8574d43eb70a4d9de1
The ninja build seems to fail consistently when doing anything related to
"obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h".
It produces the following output before eventually crashing the make job queue:
>> [218/2653] ACTION generate_bytecode_builtins_list: generate_bytecode_builtins_list_action_3931b343a4cb0bd98da4e581f6ce90fe
>> FAILED: obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h
>> cd ../../tools/v8_gypfiles; python ../../deps/v8/tools/run.py ../../out/Release/v8-qemu-wrapper ../../out/Release/bytecode_builtins_list_generator ../../out/Release/obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h
>> qemu-i386: Could not open '/lib/ld-musl-i386.so.1': No such file or directory
Return code is 255
Getting the file info from "./output/target/lib/ld-musl-i386.so.1" returns the
following:
>> ./output/target/lib/ld-musl-i386.so.1: broken symbolic link to /lib/libc.so
I'm unsure if that is what is causing my issues. From what I can tell, the qemu
wrapper should be able to resolve that symlink to the one found under the
target's lib.
I do not believe that my issue is related to Bug 14936 nor Bug 14366. I have
not had time to see if the patch available at
https://patchwork.ozlabs.org/project/buildroot/patch/20220809075704.86472-4-ardeleanalex@gmail.com/
works for my specific case.
Thanks for any help in advance!
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-10-17 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:43 bugzilla [this message]
2022-10-20 17:13 ` [Buildroot] [Bug 15061] Node.js Package fails to build against musl i386 bugzilla
2022-10-20 17:14 ` bugzilla
2022-10-26 12:59 ` bugzilla
2022-10-30 20:19 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15061-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox