From: David Laight <David.Laight@ACULAB.COM>
To: "'bugzilla@busybox.net'" <bugzilla@busybox.net>,
"buildroot@uclibc.org" <buildroot@uclibc.org>
Subject: Re: [Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04
Date: Wed, 23 Feb 2022 08:48:57 +0000 [thread overview]
Message-ID: <b56cb610ee034d80ae2afe30fb6f6351@AcuMS.aculab.com> (raw)
In-Reply-To: <bug-14366-163-zTiO0GJ8cx@https.bugs.busybox.net/>
> -----Original Message-----
> From: buildroot <buildroot-bounces@buildroot.org> On Behalf Of bugzilla@busybox.net
> Sent: 23 February 2022 08:20
> To: buildroot@uclibc.org
> Subject: [Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04
>
> https://bugs.busybox.net/show_bug.cgi?id=14366
>
> --- Comment #4 from Jens Maus <mail@jens-maus.de> ---
> I just checked the latest 2022.02-rc2 version and there the issue with not
> being able to compile nodejs v14+ on an ubuntu host still exists as outlined
> here.
>
> However, taking the workaround mentioned in
> https://gitlab.com/qemu-project/qemu/-/issues/857 I could workout a patch that
> seems to fix the issue:
>
> --- buildroot/package/nodejs/v8-qemu-wrapper.in.orig
> +++ buildroot/package/nodejs/v8-qemu-wrapper.in
> @@ -5,5 +5,6 @@
> exec @QEMU_USER@ -r @TOOLCHAIN_HEADERS_VERSION@ \
> @QEMU_USERMODE_ARGS@ \
> -L "${STAGING_DIR}/" \
> + -E LD_LIBRARY_PATH="/lib/" \
> "$@"
Except that isn't really what LD_LIBRARY_PATH path should be used for.
David
>
>
> With this patch nodejs v14+ seems to compile fine on an ubuntu 20.04 LTS host.
>
> --
> 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
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-23 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 11:35 [Buildroot] [Bug 14366] New: 2021.11-rc2: Build of nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04 bugzilla
2022-01-31 10:32 ` [Buildroot] [Bug 14366] " bugzilla
2022-01-31 10:54 ` bugzilla
2022-01-31 15:52 ` bugzilla
2022-01-31 15:56 ` [Buildroot] [Bug 14366] Nodejs " bugzilla
2022-02-04 11:03 ` bugzilla
2022-02-23 8:20 ` bugzilla
2022-02-23 8:48 ` David Laight [this message]
2022-03-01 9:49 ` bugzilla
2022-03-09 10:05 ` bugzilla
2022-03-09 10:19 ` bugzilla
2022-04-13 14:35 ` bugzilla
2022-04-13 15:16 ` bugzilla
2022-06-09 14:59 ` bugzilla
2023-09-24 16:37 ` 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=b56cb610ee034d80ae2afe30fb6f6351@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=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