From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04
Date: Mon, 31 Jan 2022 15:56:44 +0000 [thread overview]
Message-ID: <bug-14366-163-V0DPV83bx8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14366-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14366
Jens Maus <mail@jens-maus.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|2021.11-rc2: Build of |Nodejs fails with "version
|nodejs fails with "version |`GLIBC_2.34' not found" on
|`GLIBC_2.34' not found" on |Ubuntu 20.04
|Ubuntu 20.04 |
--
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 prev parent reply other threads:[~2022-01-31 15:56 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 ` bugzilla [this message]
2022-02-04 11:03 ` [Buildroot] [Bug 14366] Nodejs " bugzilla
2022-02-23 8:20 ` bugzilla
2022-02-23 8:48 ` David Laight
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=bug-14366-163-V0DPV83bx8@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