Problems building a cross compiler...

Problems building a cross compiler...

[Andrew McCall]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi Folks,

I am attempting to build a patched gcc 2.95.3 cross compiler so I can
produce targets of powerpc-*-haiku that are ELF's.  I was planning on
patching it in two phases, firstly to get gcc to compile using
- --target=powerpc-apple-haiku by duplicating all the code for
powerpc-apple-beos - if I am correct this would produce COFF or PE
binaries, the second phase would be to patch again so it produces ELF's.

I patched gcc to recognise powerpc-apple-haiku as a target, but still
use the original BFD, and configured using:

../configure --target=powerpc-apple-haiku --disable-nls
- --enable-shared=yes --enable-languages=c,c++ --prefix=/home/mccall/haiku

This worked OK, and you can see the output here:

http://www.h2o.demon.co.uk/haiku/haiku_gcc_configure.txt

However, when I run make, I eventually get the following error:

../../gcc/libgcc2.c:41: stdlib.h: No such file or directory
../../gcc/libgcc2.c:42: unistd.h: No such file or directory
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory
`/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory
`/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory
`/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
make: *** [all-gcc] Error 2

The full output can be seen here:

http://www.h2o.demon.co.uk/haiku/haiku_gcc_make.txt

I thought that it might have been my patches, so I tried the same
thing, but with the --target=powerpc-apple-beos, and this produces the
exact same error.

Can anyone suggest what the problem is?  Is it something to do with me
needing headers from BeOS/Haiku to build a cross compiler?

Thanks,

Andrew McCall

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFC356W3NPNAi0EUWURAoUZAJ9VxQJRmhTy9uairdO5vPdSNkxyPgCg3HWz
n3BbNw4yLLQ6BdPNdSQHmmo=
=d5WN
-----END PGP SIGNATURE-----

Re: Problems building a cross compiler...

[Ian Lance Taylor]

Andrew McCall <andrew.mccall@gmail.com> writes:

> However, when I run make, I eventually get the following error:
> 
> ../../gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc/libgcc2.c:42: unistd.h: No such file or directory
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory
> `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory
> `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory
> `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> make: *** [all-gcc] Error 2
> 
> The full output can be seen here:
> 
> http://www.h2o.demon.co.uk/haiku/haiku_gcc_make.txt
> 
> I thought that it might have been my patches, so I tried the same
> thing, but with the --target=powerpc-apple-beos, and this produces the
> exact same error.
> 
> Can anyone suggest what the problem is?  Is it something to do with me
> needing headers from BeOS/Haiku to build a cross compiler?

Yes, that is exactly what it is.

The simplest approach is to copy all the header files and libraries
onto the cross-host, using the same directory layout under some
directory DIR, and then configure --with-sysroot=DIR.

Ian

Re: Problems building a cross compiler...

[Andrew McCall]

Hi Ian,

Thanks for the help with my cross compile problems!

On 21 Jul 2005 09:56:16 -0700, Ian Lance Taylor <ian@airs.com> wrote:
> Andrew McCall <andrew.mccall@gmail.com> writes:
> 
> > However, when I run make, I eventually get the following error:
> >
> > ../../gcc/libgcc2.c:41: stdlib.h: No such file or directory
> > ../../gcc/libgcc2.c:42: unistd.h: No such file or directory
> > make[3]: *** [libgcc2.a] Error 1
> > make[3]: Leaving directory
> > `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> > make[2]: *** [stmp-multilib-sub] Error 2
> > make[2]: Leaving directory
> > `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> > make[1]: *** [stmp-multilib] Error 1
> > make[1]: Leaving directory
> > `/home/mccall/haiku/src/gcc-2.95.3-haiku/gcc-obj/gcc'
> > make: *** [all-gcc] Error 2

[Snip]

> > Can anyone suggest what the problem is?  Is it something to do with me
> > needing headers from BeOS/Haiku to build a cross compiler?
> 
> Yes, that is exactly what it is.
> 
> The simplest approach is to copy all the header files and libraries
> onto the cross-host, using the same directory layout under some
> directory DIR, and then configure --with-sysroot=DIR.

I have been trying to get this working since you suggested it.

I have the headers, but they come in multiple folders like this:

headers/cpp
headers/gnu
headres/libs
headers/os
headers/posix
headers/private
headers/tools

In os I have the normal "Be" headers, such as Be.h, Appkit.h etc. etc.
in posix I have the posix headers like alloca.h, assert.h and
stdlib.h.

You can see the layout here:

http://svn.berlios.de/viewcvs/haiku/haiku/trunk/headers/

I have tried using:

--with-sysroot=../../../haiku/headers
--with-sysroot=../../../haiku/headers/os
--with-sysroot=../../../haiku/headers/posix

But all of these fail with the same error.

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

RE: Problems building a cross compiler...

[Rupert Wood]

Andrew McCall wrote: 

> You can see the layout here:
> 
> http://svn.berlios.de/viewcvs/haiku/haiku/trunk/headers/
> 
> I have tried using:
> 
> --with-sysroot=../../../haiku/headers
> --with-sysroot=../../../haiku/headers/os
> --with-sysroot=../../../haiku/headers/posix

IIRC, the sysroot directory should contain subdirectories 'include' and
'lib'. By the look of it, posix is the one you need as include, although you
might want to merge in the os directory depending on what layout the apps
you want to compile expect. You could do this by making a new 'include'
directory and using cpio or similar to link in all the files in os and
posix. I don't know the convention for your OS.

I may be a few years out of date but it used to be safest to use absolute
paths for configure parameters rather than relative paths, i.e.

    --with-sysroot=/home/mccall/haiku/headers

Rup.

Re: Problems building a cross compiler...

[Andrew McCall]

On 22/07/05, Rupert Wood <me@rupey.net> wrote:
> Andrew McCall wrote:
> 
> > You can see the layout here:
> >
> > http://svn.berlios.de/viewcvs/haiku/haiku/trunk/headers/
> >
> > I have tried using:
> >
> > --with-sysroot=../../../haiku/headers
> > --with-sysroot=../../../haiku/headers/os
> > --with-sysroot=../../../haiku/headers/posix
> 
> IIRC, the sysroot directory should contain subdirectories 'include' and
> 'lib'. By the look of it, posix is the one you need as include, although you
> might want to merge in the os directory depending on what layout the apps
> you want to compile expect. You could do this by making a new 'include'
> directory and using cpio or similar to link in all the files in os and
> posix. I don't know the convention for your OS.
> 
> I may be a few years out of date but it used to be safest to use absolute
> paths for configure parameters rather than relative paths, i.e.
> 
>     --with-sysroot=/home/mccall/haiku/headers

Thanks for the reply Rupert, again, I have tried this, but I still get
the same error.  Can I not use -H or something to include multiple
directories?

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

Re: Problems building a cross compiler...

[Ian Lance Taylor]

Andrew McCall <andrew.mccall@gmail.com> writes:

> > The simplest approach is to copy all the header files and libraries
> > onto the cross-host, using the same directory layout under some
> > directory DIR, and then configure --with-sysroot=DIR.
> 
> I have been trying to get this working since you suggested it.
> 
> I have the headers, but they come in multiple folders like this:
> 
> headers/cpp
> headers/gnu
> headres/libs
> headers/os
> headers/posix
> headers/private
> headers/tools
> 
> In os I have the normal "Be" headers, such as Be.h, Appkit.h etc. etc.
> in posix I have the posix headers like alloca.h, assert.h and
> stdlib.h.

By the default gcc expects to see a Unix style file system layout,
with /lib, /usr/include, /usr/lib, etc.  The header files would
normally be found in SYSROOT/usr/include, and, e.g., stdlib.h would be
found in SYSROOT/usr/include/stdlib.h.

You could shuffle your header files around to meet Unix expectations.
Or you could sort out INCLUDE_DEFAULTS for the particular case of
CROSS_COMPILER and TARGET_SYSTEM_ROOT.  See cppdefault.c.  I see an
instance of INCLUDE_DEFAULT in config/i386/beos-elf.h, although the
directories there do not appear to match the directories you listed
above.

I'm afraid that you have an unusual scenario, and you are going to
have to learn how gcc handles include file searching.

Ian