[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130813160052.GD221@brightrain.aerifal.cx>
Date: Tue, 13 Aug 2013 12:00:52 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: problems with dynamic linking since 0.9.1
On Tue, Aug 13, 2013 at 04:53:00PM +0200, Szabolcs Nagy wrote:
> * Jens <jensl@...s.mine.nu> [2013-08-13 13:18:27 +0200]:
> > On Tue, 13 Aug 2013, Szabolcs Nagy wrote:
> > >
> > >you didn't tell us the problem
> > >
> > >at least show a crashing dynamic linked executable
> > >with straced loader and musl ldd output
> >
> > Sorry. Its actually linking the binary that doesnt work.
> >
>
> ah ok i did not see that
>
> i'd check libc.so if there is some obvious error
> ld should be able to handle it
> (eg file libc.so, readelf -a libc.so, nm -D libc.so, or just ./libc.so)
>
> since you use landley's weird toolchain it may be a
> problem with the old binutils
Indeed, that toolchain is probably already using its own gcc wrapper
around the real gcc located at a different path. Neither wrapper is
sufficiently transparent to allow another wrapper around it to
function 100% correctly, so I would guess this is your problem. See if
you can find the location of the real gcc binary and have musl-gcc run
that, or perhaps just get a compiler from the musl-cross package or
compile your own toolchain.
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.
