[Beowulf] GLIBC_3.4.x/GLIBCXX_3.4.x not found on CentOS 7.x?

[Ryan Novosielski]

Hi Beowulfers:

What do you folks use (besides use Singularity or similar) for software that for whatever reason balks because it asks for GLIBC/GLIBCXX 3.4.20 or newer on CentOS 7.x?

From what I’ve read, it’s not safe to build it in an alternate location and use LD_LIBRARY_PATH to have software call it. I am almost certain that this is true of the GLIBC dependencies. I’m less sure of the GLIBCXX dependency. And I know that whenever we build an alternate copy of GCC (like 4.9.x or newer), we create a software module that /does/ in fact place a newer libstdc++.so.6 into the LD_LIBRARY_PATH. What I’ve read /might/ be safe, but problematic in some cases (and no help at all in the case of binary distributions) is using -rpath type stuff at build time. There appears to be a lot of conflicting information out there, and some “just throw a newer libstdc++.so.6 library in a lib directory,” and some “that’s not such a great idea” posts right below them.

Do I misunderstand the situation? Is there a difference between software that demands a newer GLIBC vs. GLIBCXX? Does anyone have a reference one can trust on this subject?

Thanks -- I know there are some really highly qualified people on this list. :-D

--
____
|| \\UTGERS,  	 |---------------------------*O*---------------------------
||_// the State	 |         Ryan Novosielski - novosirj at rutgers.edu
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
||  \\    of NJ	 | Office of Advanced Research Computing - MSB C630, Newark
     `'

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: Message signed with OpenPGP
URL: <http://www.beowulf.org/pipermail/beowulf/attachments/20180619/214c6dd5/attachment.sig>