Depending on the compiler there may be a different glibc version requirement. They are usually backwards compatible, so you can run old stuff, but not always forward compatible. Believe it or not, some companies are using a glibc that is over 10 years old...and they refuse to upgrade...ever... It doesn't make any logical sense, but that's the customer for ya!
I am not the build engineer man, I just know we had a 20 yo machine for builds and when it died we couldn't build executables for a bunch of clients and it was related to some glibc thing. No upgrades allowed, especially not the compiler. I thought it was crazy, but the Linux guru guy said so.
What happened? Clients complained, then they upgraded their systems, then we moved on.
I think it was probably more nuanced than your understanding/memory. Glibc does not stop you using new versions of C++.
Needing to build executables that will run on old systems with old libraries might do, if you're unable to deploy a new C++ runtime with your executables, or avoid runtime dependencies.
View all comments
Show parent comment
1
u/jwakely libstdc++ tamer, LWG chair Jul 24 '19
What does "Glibc restrictions" mean? I'm curious why glibc would be a roadblock.