Re: self-contained cross-compiler?

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

On Tuesday 16 December 2003 12:25, Roman Duka wrote:
> the key is to
> run "configure" with --disable-nls option
> run "make configure-host"
> run "make configure-target"
> run "make LDFLAGS=-all-static"
> run "make install"
>
> Note: you need to change line "make LDFLAGS=-all-static all" to "make
> LDFLAGS=-all-static" otherwise build will fail
> anyway below is the function for building static binutils from my scripts
>
> mkbinutils() {
>
> echo "Unpacking binutils sources" \
> && cd $BUILDDIR && unpacksrc $BINUTILS \
> && echo "Patching binutils source tree" \
> && patchsrc $BINUTILS \
> && mkdir -p $BUILDDIR/binutils-build \
> && cd $BUILDDIR/binutils-build \
> &&
> if test '!' -f Makefile
> then
>      $BUILDDIR/$BINUTILS/configure --target=$MTARGET
> --prefix=$INSTALLDIR --disable-nls
> fi \
> && make configure-host \
> && make configure-target \
> && make LDFLAGS="-all-static" \
> && make install \
> && cd .. \
> && rm -rf $BUILDDIR/binutils* \
> && if test ! -x $INSTALLDIR/bin/$MTARGET-ld
> then
>      return 1
> fi
>
> #---------------------------------------------------------
> }

Hi Roman;

  Using the information you provided, I was able to generate an arm9 
statically-linked binutils by hand, thank you very much...

  I wonder why I am unable to do this with crosstool directly.

  I'm looking at crosstool again, trying to grok the difference.

Thanks for the help,
Ken Wolcott


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