2 ms·
What PHK misses is that the messiness he observes is not inherent in "the bazaar", but in the environment which gave rise to autoconf and libtool: multiple, com
by bitwize 9y ago
What PHK misses is that the messiness he observes is not inherent in "the bazaar", but in the environment which gave rise to autoconf and libtool: multiple, competing cathedrals that didn't share knowledge and couldn't agree on the basics. A standard set of options to ld(1) for dynamic libraries would have been nice in 1988, but I too want a pony. In the 1980s not everybody agreed even on how to do dynamic libraries. There were three major competing implementations: loading dynamic libs at fixed memory addresses (e.g., old-school a.out Linux), position-independent code (e.g., modern Linux), or monkeypatching the in-memory image to point all function calls to dynamic symbols to their proper locations (e.g., Windows). Which one an OS chose had profound implications for what the linker could do and how. So getting a universal standard for dynamic-lib linker flags at the dawn of POSIX was a pipe dream. hence the need for libtool.
In a universe of abundant open source these problems are sometimes stupid easy to solve. The x86Open project was a consortium to define a common ABI for Unix implementations on x86 hardware. But since all the vendors involved (including a couple of open-source BSDs) already shipped Linux kernel personalities for their OS, the only business x86Open ever did was to declare "Linux ELF binaries" the standard and then disband itself.