Re: Building mips*-linux-gnu using --with-newlib

[cgd at broadcom dot com]

At Sun, 19 Oct 2003 19:15:40 +0000 (UTC), "Richard Sandiford" wrote:
> Dunno how standard this is, but I tend to build a mips*-linux-gnu
> sysroot as follows:
> 
>    - build a bare-bones gcc, configured using:
>         --with-newlib --disable-shared --disable-threads
>         --enable-languages=c
>    - use it to build & install glibc
>    - build a full compiler, no special configure options
>    - use it to build the rest of the sysroot

where the rest of the sysroot includes glibc, or not?

does this actually do "the right thing"?  In particular, IIRC (it's
been a few weeks since I looked), glibc links against gcc-built
libraries, so if the ones used to build glibc aren't "right" I
wouldn't trust the glibc build entirely.

currently, I do a multi-pass thing: build gcc, build static glibc,
build gcc, build shared glibc, build final gcc.

gcc first pass:
   configure with:                 
           --enable-languages=c --disable-threads --disable-shared
   make/install with:
           ALL_TARGET_MODULES= CHECK_TARGET_MODULES= INSTALL_TARGET_MODULES=

gcc second pass:
   configure with:                 
           --enable-languages=c --disable-threads --with-sysroot=...
   make/install with:
           ALL_TARGET_MODULES= CHECK_TARGET_MODULES= INSTALL_TARGET_MODULES=

gcc third pass:
   configure with:
                --enable-languages=c,c++,f77 --with-sysroot=$sysroot --enable-threads
   no special make/install args.



chris