Skip to contentSkip to conversation

New: 2021.11-rc2: Build of nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

Buildroot [email protected] 2 participants 15 messages Nov 20, 2021 – Sep 24, 2023

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=14366

            Bug ID: 14366
           Summary: 2021.11-rc2: Build of nodejs fails with "version
                    `GLIBC_2.34' not found" on Ubuntu 20.04
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

Target Milestone: ---

After upgrading from 2021.08.2 to the latest 2021.11-rc2 the following error appear when compiling nodejs-14.18.1:

-- cut here --

LD_LIBRARY_PATH=/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/lib.host:/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/v8_gypfiles; mkdir -p /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/include/inspector /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/src/inspector/protocol;
python ../../deps/v8/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../deps/v8/third_party --output_base
"/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/src/inspector"
--config ../../deps/v8/src/inspector/inspector_protocol_config.json
--inspector_protocol_dir ../../deps/v8/third_party/inspector_protocol

LD_LIBRARY_PATH=/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/lib.host:/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/v8_gypfiles; mkdir -p /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/include/inspector /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/src/inspector/protocol;
python ../../deps/v8/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../deps/v8/third_party --output_base
"/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/inspector-generated-output-root/src/inspector"
--config ../../deps/v8/src/inspector/inspector_protocol_config.json
--inspector_protocol_dir ../../deps/v8/third_party/inspector_protocol
/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator) /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator) /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/bytecode_builtins_list_generator)
make[3]: *** [tools/v8_gypfiles/generate_bytecode_builtins_list.target.mk:13:
/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/out/Release/obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h]
Error 1
make[3]: *** Waiting for unfinished jobs....
rm e730c40db4707fa90e26f9a1f4e233545a966191.intermediate
f851aa033254e58b7e35f943f6814ef5e8f9642a.intermediate
make[2]: *** [Makefile:109: node] Error 2
make[2]: Leaving directory
'/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1'
make[1]: *** [package/pkg-generic.mk:294:
/home/damato/projekte/linux/RaspberryMatic/build-raspmatic_ova/build/nodejs-14.18.1/.stamp_built]
Error 2
make[1]: Leaving directory
'/home/damato/projekte/linux/RaspberryMatic/buildroot-2021.11-rc2'
make: *** [Makefile:51: build] Error 2
-- cut here --

Thus, it looks like the host system libc.so.6 is used for the "bytecode_builtins_list_generator" tool that is automatically build during the nodejs-14.18.1 build run. However, as buildroot 2021.11 introduced GLIBC_2.34 the execution of "bytecode_builtins_list_generator" fails because Ubuntu 20.04 does not come with a glibc with GLIBC_2.34 symbols in libc.so. Thus, the dedicated compiled 2.34 glibc for the host in "host/x86_64-buildroot-linux-gnu/sysroot/lib" should be used instead so that the "bytecode_builtins_list_generator" tool can be correctly executed.

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#1 lore raw

[Buildroot] [Bug 14366] 2021.11-rc2: Build of nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

https://bugs.busybox.net/show_bug.cgi?id=14366

Frank Rogall <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Frank Rogall <[email protected]> --- Bug still exists in 2021.11.1 with nodejs-14.18.3 Ubuntu 20.04.3 LTS

/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator)
make[3]: *** [tools/v8_gypfiles/generate_bytecode_builtins_list.target.mk:13:
/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h] Error 1

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#2 lore raw

[Buildroot] [Bug 14366] 2021.11-rc2: Build of nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

Frank Rogall <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |2021.11.1

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#3 lore raw

[Buildroot] [Bug 14366] 2021.11-rc2: Build of nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #2 from Jens Maus <[email protected]> --- I can confirm that this issue still exists in 2021.11.1.

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#4 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

Jens Maus <[email protected]> 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                |
Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#5 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #3 from [email protected] ---
I have the same issue. It seems that qemu used in v8-qemu-wrapper.in caused this issue. Build nodejs for aarch64 on x86_64 works fine, but building for x86_64 on x86_64 failed. I entered a bug request for qemu
(https://gitlab.com/qemu-project/qemu/-/issues/857).

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#6 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #4 from Jens Maus <[email protected]> ---
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:

package/nodejs/v8-qemu-wrapper.in renamed from package/nodejs/v8-qemu-wrapper.in.orig +1 -0
@@ -5,5 +5,6 @@
 exec @QEMU_USER@ -r @TOOLCHAIN_HEADERS_VERSION@ \
     @QEMU_USERMODE_ARGS@ \
    -L "${STAGING_DIR}/" \
+   -E LD_LIBRARY_PATH="/lib/" \
     "$@"
 

With this patch nodejs v14+ seems to compile fine on an ubuntu 20.04 LTS host.

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#7 lore raw

Re: [Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

Quoted 20 lines

-----Original Message-----
From: buildroot <[email protected]> On Behalf Of [email protected]
Sent: 23 February 2022 08:20
To: [email protected]
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 <[email protected]> ---
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:

package/nodejs/v8-qemu-wrapper.in line 9

Quoted 5 lines
package/nodejs/v8-qemu-wrapper.in renamed from package/nodejs/v8-qemu-wrapper.in.orig +1 -0
@@ -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

Quoted 11 lines

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
[email protected]
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
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

#8 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #5 from Frank Rogall <[email protected]> --- Bug still exists in 2021.11.2 with nodejs-14.18.3 Ubuntu 20.04.3 LTS

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#9 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

Frank Rogall <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

            Version|2021.11.1                   |2022.02
           Severity|major                       |blocker

--- Comment #6 from Frank Rogall <[email protected]> --- This Bug is still in 2022.02

LD_LIBRARY_PATH=/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/lib.host:/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/v8_gypfiles; mkdir -p /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/obj/gen/generate-bytecode-output-root/builtins-generated;
python ../../deps/v8/tools/run.py
"/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/v8-qemu-wrapper" "/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator" "/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h" /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator) /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator) /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/bytecode_builtins_list_generator)
make[3]: *** [tools/v8_gypfiles/generate_bytecode_builtins_list.target.mk:13:
/home/fr/work/egate/x/egate/build/nodejs-14.18.3/out/Release/obj/gen/generate-bytecode-output-root/builtins-generated/bytecodes-builtins-list.h] Error 1

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#10 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #7 from Jens Maus <[email protected]> --- (In reply to Frank Rogall from comment #6)

I could verify that this issue still exists in 2022.02. However, my mentioned workaround (cf. https://bugs.busybox.net/show_bug.cgi?id=14366#c4) still works.

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#11 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #8 from Frank Rogall <[email protected]> --- Still in 2022.02.1

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#12 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #9 from Frank Rogall <[email protected]> --- (In reply to Jens Maus from comment #7)
Patch is working on 2022.02.1

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#13 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

--- Comment #10 from Felix Schmidt <[email protected]> --- (In reply to Frank Rogall from comment #9)
I'm having a similar issue, with host=x86_64 and target=i686 (32bit).

Here this patch does not work. This is my workaround:

package/nodejs/v8-qemu-wrapper.in renamed from package/nodejs/v8-qemu-wrapper.in.orig +1 -0
@@ -5,5 +5,6 @@
 exec @QEMU_USER@ -r @TOOLCHAIN_HEADERS_VERSION@ \
     @QEMU_USERMODE_ARGS@ \
    -L "${STAGING_DIR}/" \
+   -E LD_LIBRARY_PATH="${STAGING_DIR}/lib:${STAGING_DIR}/usr/lib/" \
     "$@"
 
Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#14 lore raw

[Buildroot] [Bug 14366] Nodejs fails with "version `GLIBC_2.34' not found" on Ubuntu 20.04

In reply to [email protected]

https://bugs.busybox.net/show_bug.cgi?id=14366

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]

--- Comment #11 from Yann E. MORIN <[email protected]> --- Jens, All,

Fixed as of commit 278d1db56b.

Regards,
Yann E. MORIN.

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot