supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Lasse Kliemann <lasse-list-supervision-2007@plastictree.net>
To: Mike Buland <xagafinelle@gmail.com>
Cc: supervision@list.skarnet.org
Subject: Re: Problems Compiling with glibc 2.12.1
Date: Mon, 7 Feb 2011 00:12:09 +0100	[thread overview]
Message-ID: <20110206231209.GA10928@lasse.mail.plastictre.net> (raw)
In-Reply-To: <AANLkTi=0WNSQAgqYrPOG0ixMweNUrpeVzHnah-9pkWXL@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

* Message by -Mike Buland- from Tue 2010-11-09:

> I just wanted to let everyone know  that I've come across a strange
> problem compiling runit.  The issue seems to be with glibc version
> 2.12.1, earlier versions did not exhibit this.  I've also tried GCC
> 4.5.1, 4.5.0, and 4.4.5.  The binutils version I'm using is 2.20.1.
> 
> When compiling, the runit and runit-init programs link statically, and
> the result does not appear to be a valid executable program.  The
> system complains that there is no valid entry point.  Interestingly
> enough, I can't get this to happen with any programs that aren't runit
> and runit-init.  Also, the problem is not evident when linking against
> dietlibc.  The executables I made with dietlibc are fine.
> 
> I don't think this is an issue for runit, actually, especially since
> there is a workaround, but it is a concern for the glibc developers,
> but who knows when they'll get around to fixing it.  I thought the
> list in general could benefit from my somewhat limited research into
> the problem.  I'm also in the process of figuring out if this is a new
> bug for the glibc devs or not so I can report it to them.
> 
> Also, I'm running a 32bit x86 system, and I've tried it on a couple
> different processors, with a few different compile options in place
> while building glibc, always the same results.

I get "unexpected reloc type in static binary" and a segfault:

  bash-4.0$ package/check 
  Checking commands in ./command...
  + cd compile
  + exec make check
  ./check-local chpst runit runit-init runsv runsvchdir runsvdir sv svlogd utmpset
  Checking chpst...
  Checking runit...
  unexpected reloc type in static binarySegmentation fault
  139
  runit failed.
  make: *** [check] Error 1

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".

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-02-06 23:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 15:29 Mike Buland
2011-02-06 23:12 ` Lasse Kliemann [this message]
2011-02-07  0:50   ` Laurent Bercot
2011-02-07  2:09     ` Charlie Brady
2011-02-07  7:56       ` Laurent Bercot
2011-02-08  0:16     ` Lasse Kliemann
2011-06-13 13:01   ` Robin Bowes
2011-06-13 13:38     ` Laurent Bercot
2011-06-13 17:19       ` Robin Bowes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110206231209.GA10928@lasse.mail.plastictre.net \
    --to=lasse-list-supervision-2007@plastictree.net \
    --cc=supervision@list.skarnet.org \
    --cc=xagafinelle@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).