This is the mail archive of the
mailing list for the binutils project.
Re: differences in generated ldscripts for native and cross builds
- From: Alan Modra <amodra at gmail dot com>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: binutils <binutils at sourceware dot org>
- Date: Wed, 9 Dec 2015 09:45:02 +1030
- Subject: Re: differences in generated ldscripts for native and cross builds
- Authentication-results: sourceware.org; auth=none
- References: <20151206225447 dot GJ5966 at bubble dot grove dot modra dot org> <20151208170644 dot A38E3CA42 at oc7340732750 dot ibm dot com>
On Tue, Dec 08, 2015 at 06:06:44PM +0100, Ulrich Weigand wrote:
> Alan Modra wrote:
> > Where we might get into trouble is on systems that use old startup
> > files lacking code to call constructor function pointers in
> > .init_array. For glibc that means 2002 vintage code, I think.
> I just noticed this change broke spu-elf; most newlib targets (with
> the sole exception of ARM/AArch64) still do not support .init_array.
> But I guess at this point I can live with having to specify
> --disable-initfini-array when building current binutils for SPU ...
That's a pain. I did glance over current newlib before making the
change, and saw configure tests for init_array plus
newlib/libc/misc/init.c:__libc_init_array. I didn't notice that
__libc_init_array is only used on arm/aarch4. :-(
Australia Development Lab, IBM