Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150702165431.GH1173@brightrain.aerifal.cx>
Date: Thu, 2 Jul 2015 12:54:31 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Error relocating libc.so: (...): symbol not found

On Thu, Jul 02, 2015 at 06:16:39PM +0200, Laurent Bercot wrote:
> 
>  Hi,
>  I just pulled the latest musl git head and compiled it.
> Previously I was using a git version from right before 1.1.9
> or something. (Sorry, I didn't take notes, I can't tell you
> exactly what it was.)
> 
>  Now, when I run ldd on a static binary (compiled with either
> that new musl or a previous version), I get the following
> messages:
> 
> Error relocating libc.so: __muldc3: symbol not found
> Error relocating libc.so: __mulsc3: symbol not found
> Error relocating libc.so: __mulxc3: symbol not found
> 
> before the expected
> ldd: (binary): Not a valid dynamic program
> 
>  This is on x86_84 with gcc-4.2.1.
> 
>  Is anything wrong with my binaries or new musl installation,
> or are those spurious messages?

It sounds like a broken libc.so. There should not be dynamic symbol
references or definitions for libgcc symbols in libc.so. Is it
possible that your toolchain is doing something wacky that links
shared libgcc even when we try to do static libgcc?

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.