[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151117152728.GX3818@brightrain.aerifal.cx>
Date: Tue, 17 Nov 2015 10:27:28 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: some odd library loading errors
On Tue, Nov 17, 2015 at 04:23:56PM +0100, Szabolcs Nagy wrote:
> * u-uy74@...ey.se <u-uy74@...ey.se> [2015-11-17 13:14:29 +0100]:
> > The environment:
> > Linux 3.# on x#86
> > binutils 2.24
> > musl 1.1.8 compiled for i486
> > gcc 5.2.0
> >
> > (the gcc has arch=i486 as the default)
> >
> > No oddities were observed with the above until trying to use libatomic
> > which is provided by gcc-5.2.0.
> >
> > The test case:
> >
> > $ cat >a.c <<____
> > int main(){ return 0; }
> > ____
> >
> > $ gcc -o a a.c -L<path-to-gcc-5.2.0-libs> -latomic
> >
> > $ LD_LIBRARY_PATH=<path-to-gcc-5.2.0-libs> ./a
> > Error relocating <path-to-gcc-5.2.0-libs>/libatomic.so.1: __atomic_store_8: symbol not found
> > Error relocating <path-to-gcc-5.2.0-libs>/libatomic.so.1: __atomic_exchange_8: symbol not found
> > Error relocating <path-to-gcc-5.2.0-libs>/libatomic.so.1: __atomic_load_8: symbol not found
> > Error relocating <path-to-gcc-5.2.0-libs>/libatomic.so.1: __atomic_compare_exchange_8: symbol not found
> >
>
> this is a known issue, they use the gnu ifunc extension of
> elf to dispatch between different implementations based on
> the machine at library loadtime.
Is there something we need to add to the musl patches to disable this?
I would like to make sure both that it's going upstream and that I
have a patch in my toolchain build repo.
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.
