Hacker News Reader

In this example the problem is caused by the dynamic linker shipping with a hard glibc dependency, so FHS doesn't really change much.

Setting LD_LIBRARY_PATH pretty much solves any FHS problem once you get past the linker.

View on HN

The dynamic linker is part of glibc, so if you're shipping multiple glibcs, ship multiple dynamic linkers as well and let each application use the linker it needs.

LD_LIBRARY_PATH users deserve the death sentence.

Why? It’s just PATH for libraries.

Because it's an environment variable, and thus will have an (often undesired) effect on child processes. This information should instead be encoded into the binaries and libraries themselves, with things like DT_RUNPATH and DT_RPATH.

Reply on news.ycombinator.com