This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gold vs. CT_STATIC_TOOLCHAIN


On Wed, Dec 14, 2011 at 01:09:21AM +0100, Yann E. MORIN wrote:
> Johannes, All,
> 
> On Friday 02 December 2011 14:24:50 Johannes Stezenbach wrote:
> > with CT_STATIC_TOOLCHAIN ./scripts/build/binutils/binutils.sh
> > adds -all-static to LDFLAGS.  However, -all-static is a libtool
> > option and gold is not libtoolized.  Maybe cg-ng should just
> > disable gold when CT_STATIC_TOOLCHAIN is selected?
> 
> It works here for me:
> 
>   $ file bin/armeb-unknown-linux-uclibcgnueabi-ld.gold 
>   bin/armeb-unknown-linux-uclibcgnueabi-ld.gold: ELF 64-bit LSB executable,
>   x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18,
>   not stripped
> 
> So, it is a statically-linked executable, exactly what we wanted.
> 
> How does it break for you?

I didn't save the log so I'd have to rebuild to find out
(which I'll do asap), but IIRC it was similar to

$ gcc foo.c -all-static
gcc: error: unrecognized option â-all-staticâ

In case it matters, I used the newest available binutils,
(IIRC binutils-2.21.53 in ct-ng-1.13.2,  and now 2.22
with ct-ng from hg.


Thanks
Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]