You are here |
mpark.github.io | ||
| | | |
theartofmachinery.com
|
|
| | | | ||
| | | |
susam.net
|
|
| | | | ||
| | | |
denniskubes.com
|
|
| | | | ||
| | | |
jmmv.dev
|
|
| | 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?... |