/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version CXXABI_1.3.8′ not found

by

Add the library’s path to the LD_LIBRARY_PATH environment variable

TL;DR

GCC requires you to tell it where your library is located manually when it can’t find the right version, which can be done in a few ways. One is adding it to the LD_LIBRARY_PATH.

export LD_LIBRARY_PATH="/usr/local/lib64/:$LD_LIBRARY_PATH"

For some, the library path will be /usr/local/lib64/. Others have reported the library path /usr/lib/x86_64-linux-gnu/ working for them instead.

Why do we need to add the library to LD_LIBRARY_PATH?

When you compile and install GCC it puts the libraries in one of these directories, but that’s all it does. According to the FAQs for libstdc++, the error that we got means that the dynamic linker found the wrong version of the libstdc++ shared library. Because the linker can’t find the right version, we have to tell it where to find the libstdc++ library.

The simplest way to fix this is to use the LD_LIBRARY_PATH environment variable, which is a colon-separated list of directories in which the linker will search for shared libraries.

There are other ways as well to fix this issue. You can find this and the other solutions mentioned briefly when you install gcc if you read the make output:

Libraries have been installed in:

/usr/local/lib/../lib32

If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR’ flag during linking and do at least one of the following:

  • add LIBDIR to the `LD_LIBRARY_PATH’ environment variable during execution
  • add LIBDIR to the `LD_RUN_PATH’ environment variable during linking
  • use the `-Wl,-rpath -Wl,LIBDIR’ linker flag
  • have your system administrator add LIBDIR to `/etc/ld.so.conf’

See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages.

Grr, that was simple! Also, “if you ever happen to want to link against the installed libraries,” seriously?

More Related Contents:

  1. some problems about c++ try catch [closed]
  2. How do I find the location of the executable in C? [duplicate]
  3. Child process receives parent’s SIGINT
  4. Spinlock versus Semaphore
  5. fork() and output
  6. How to set breakpoints on future shared libraries with a command flag
  7. Is there an equivalent to WinAPI’s MAX_PATH under linux/unix?
  8. print call stack in C or C++
  9. C++ Dynamic Shared Library on Linux
  10. How to get memory usage at runtime using C++?
  11. How can I create directory tree in C++/Linux?
  12. C++ cross-compiler from Windows to Linux [closed]
  13. What are the differences between .so and .dylib on macOS?
  14. In C how do you redirect stdin/stdout/stderr to files when making an execvp() or similar call?
  15. Checking if a directory exists in Unix (system call)
  16. How to create a single instance application in C or C++
  17. Send and Receive a file in socket programming in Linux with C/C++ (GCC/G++)
  18. Seeking and reading large files in a Linux C++ application
  19. How to disassemble a binary executable in Linux to get the assembly code?
  20. Cancelling a thread using pthread_cancel : good practice or bad
  21. Linking libstdc++ statically: any gotchas?
  22. How to set up googleTest as a shared library on Linux
  23. Set environment variables in C
  24. Cross Platform Floating Point Consistency
  25. C++ error: undefined reference to ‘clock_gettime’ and ‘clock_settime’
  26. How do you get the icon, MIME type, and application associated with a file in the Linux Desktop?
  27. Default libraries linked in by gcc?
  28. Undefined reference to process(std::__cxx11::basic_string … ) when compiling affdex linux sample applications
  29. Why do I see 400x outlier timings when calling clock_gettime repeatedly?
  30. Linux C++: how to profile time wasted due to cache misses?

Leave a Comment