[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110817133913.GX132@brightrain.aerifal.cx>
Date: Wed, 17 Aug 2011 09:39:13 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Compilation error
On Wed, Aug 17, 2011 at 12:33:28PM +0200, Szabolcs Nagy wrote:
> > the only change to the linker flags is -L/path/to/pcclibs -lpcc
> > instead of -lgcc, so either pcc does not call ld properly
> > or there is some issue with -lpcc
> >
>
> i've just rechecked this and the problem simply was that
> libpcc.a was not compiled with -fPIC
It's disturbing that this made a difference. There should be no global
data needed by libpcc, and if there is some needed, I question what
it's doing and whether it's really safe...
> (it used to work because i didn't specify -lpcc when building libc.so
> and later i only tried dynamic linking with pcc
> which adds -lpcc automatically so there were no missing symbols)
This still need not work; it will result in PLT relocations in libc.so
which could crash if libpcc is needed prior to relocation. And it will
badly hurt runtime performance.
> but i guess it would be nice if musl implemented long long arithmetics
> and made -lpcc/-lgcc unnecessary
Yes..
> (i'm not sure where alloca should go, pcc does not provide it)
WTF? alloca cannot be implemented as a function. Does gcc provide an
alloca function?
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.
