Re: Problems Compiling with glibc 2.12.1

[Laurent Bercot <ska-supervision@skarnet.org>]

> This is with Glibc 2.13. Somewhat older Glibc versions work 
> alright, for instance 2.11.2. As a workaround (or fix), I changed 
> src/conf-ld to call "gcc" and not "gcc -s".

 Static linking is broken in recent glibcs. The GNU people have lost
their minds for quite a long time now.

 The runit package should not try and forcefully link executables
statically, even important executables like runit and runit-init.
Other init systems provide a dynamically-linked "init" binary and
they work (at a price, of course: the demented requirements of the
Upstart "init" binary, for instance, make booting impossible if you
don't have libdbus on your root filesystem). The decision of linking
statically or dynamically should ultimately be left to the user.

 Of course, the runit documentation could mention that it's a good
idea to statically link vital binaries (such as the Process One binary),
and that on Linux systems, glibc does not allow it. The documentation
could then point Linux users to sane libcs like dietlibc or uClibc -
to use the latter, I've been very happy with the uClibc toolchains
provided by Aboriginal Linux at landley.net/aboriginal/.

-- 
 Laurent