Re: self-contained cross-compiler?

[Ken Wolcott <ken dot wolcott at med dot ge dot com>]

> > On Tuesday 16 December 2003 10:25, Roman Duka wrote:
> >>Dan Kegel wrote:
> >>>By the way, if just linking -static doesn't work out, Ken might
> >>>consider building his tools in the LSB build environment,
> >>>assuming he can coax his users to load the LSB support package.
> >>>- Dan
> >>
> >>i think Ken managed to build static gcc compiler, only binutils were
> >>dynamically linked, that's because he used "LDFLAGS=-static" when
> >>building binutils, which doesn't create all statically linked binutils,
> >>he should use "LDFLAGS=-all-static" instead, when building binutils,
> >>that should do the trick.
>
> don't edit Makefile, you need to edit script which runs the "configure"
> and "make" commands
> try the following sequence of lines when configuring and building
> binutils (note: make sure to run "make configure-host" or a static build
> will fail. Ref
> http://linuxfromscratch.mirror.ac.uk/lfs/view/stable/chapter05/binutils-pas
>s1.html)
>
> configure --prefix=<yourprefix> <other_args> --disable-nls
> make configure-host
> make LDFLAGS="-all-static"
> make install

Roman;

  I'm using crosstool to generate the cross tool chain.  I've only edited 
crosstool.sh to change the make call(s), I've not edited the Makefile.

  I'll take another look at LFS in general (*shudder*) and your specific 
mention of LFS...

Thanks,
Ken

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com