Explore >> Select a destination


You are here

mpark.github.io
| | theartofmachinery.com
12.7 parsecs away

Travel
| |
| | susam.net
15.7 parsecs away

Travel
| |
| | denniskubes.com
24.3 parsecs away

Travel
| |
| | jmmv.dev
100.4 parsecs away

Travel
| In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?...