Menu

GLIBCXX_3.4.29 not found - and why copying libstdc++ does not fix it
πŸ“°

GLIBCXX_3.4.29 not found - and why copying libstdc++ does not fix it

DEV Community: dockerΒ·Weifeng LiuΒ·3 days ago
#Bdtnmb6X
#devtodocker#devto#dev#libstdc#newer
Reading 0:00
15s threshold

Short answer

GLIBCXX_3.4.29 is a version tag in libstdc++ (the C++ standard library shipped with GCC),

not in glibc. The binary was built with a newer GCC than the target host has, so the

target's libstdc++.so.6 does not carry that symbol version.

The fix is to build with an older toolchain, link the C++ runtime statically, or run

inside an image that matches. Copying libstdc++.so.6 from the newer machine does

not work β€” it fails one layer deeper, with a glibc error. Proof below.

First: confirm which version is missing

./your-binary # ./app: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found

Enter fullscreen mode

Exit fullscreen mode

Then ask the target host what it can offer:

grep -aoE 'GLIBCXX_3\.4\.[0-9]+' /usr/lib/x86_64-linux-gnu/libstdc++.so.6 \ | sort -V | tail -1 # GLIBCXX_3.4.30

Enter fullscreen mode

Exit fullscreen mode

And ask the binary what it needs:

readelf --version-info ./app | grep GLIBCXX | head -20

Enter fullscreen mode

Exit fullscreen mode

If…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.