From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2066 Path: news.gmane.org!not-for-mail From: Laurent Bercot Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Problems Compiling with glibc 2.12.1 Date: Mon, 7 Feb 2011 01:50:29 +0100 Message-ID: <20110207005029.GA25415@skarnet.org> References: <20110206231209.GA10928@lasse.mail.plastictre.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1297039694 8623 80.91.229.12 (7 Feb 2011 00:48:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 7 Feb 2011 00:48:14 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-2300-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Feb 07 01:48:09 2011 Return-path: Envelope-to: gcsg-supervision@lo.gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1PmFGy-0006WU-T8 for gcsg-supervision@lo.gmane.org; Mon, 07 Feb 2011 01:48:08 +0100 Original-Received: (qmail 28250 invoked by uid 76); 7 Feb 2011 00:50:29 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 28240 invoked by uid 1000); 7 Feb 2011 00:50:29 -0000 Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20110206231209.GA10928@lasse.mail.plastictre.net> User-Agent: Mutt/1.4i Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2066 Archived-At: > 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