Explore >> Select a destination
|
You are here 
|
serokell.io | ||
| | | | |
blog.kummerlaender.eu
|
|
| | | | | Adrian Kummerländer's blog on software development, linux and open source | |
| | | | |
earthly.dev
|
|
| | | | | Learn what Nix is and how it can revolutionize software development with its unique approach to package management and operating system configurati... | |
| | | | |
blog.ysndr.de
|
|
| | | | | How I use Nix to manage the development and CI of this blog | |
| | | | |
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?... | ||
