Cross Linux/x86 to Solaris2.10/x86-64 compiler build problem

[Alex Bennee]

On Mon, 2007-03-19 at 21:45 +0000, Michael Wetherell wrote:
> On Monday 19 Mar 2007 21:33, Alex Bennee wrote:
> > I'm not sure if this is a binutils problem or something funky in my
> > configure for gcc. gcc fails to link while building libgcc:
> <snip>
> These worked for me this morning:
> 
> $ ../binutils-070315/configure --build=i586-pc-linux-gnu 
> --host=i586-pc-linux-gnu --target=i386-pc-solaris2.10 --prefix=$prefix 
> --disable-nls --mandir=/tmp --infodir=/tmp --with-sysroot=$sysroot
> 
> $ ../gcc-4.1.1/configure --build=i586-pc-linux-gnu 
> --host=i586-pc-linux-gnu --target=i386-pc-solaris2.10 --prefix=$prefix 
> --disable-nls --mandir=/tmp --infodir=/tmp --enable-languages=c,c++ 
> --disable-libstdcxx-pch --with-sysroot=$sysroot --with-gnu-ld 
> --with-gnu-as

Hmmm so using sysroot instead of the header/libs options gcc now fails
with:

The directory that should contain system headers does not exist:
  /export/toolchain/build-install/i686-sun-solaris2.10/sys-include
make[2]: *** [stmp-fixinc] Error 1
make[2]: Leaving directory
`/export/toolchain/gcc-4.1.2.git/host-i686-pc-linux-gnu/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/export/toolchain/gcc-4.1.2.git'
make: *** [all] Error 2

But my sysroot certainly has stuff in it.

Whats the process for sysroot? Does binutils copy what is needed into
your prefixed build dir or should all the builds be referencing the
sysroot directly?

-- 
Alex Bennee <kernel-hacker@bennee.com>