public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Andrew McCall <andrew.mccall@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problems building a cross compiler...
Date: Thu, 21 Jul 2005 16:56:00 -0000	[thread overview]
Message-ID: <m3pstcnln3.fsf@gossamer.airs.com> (raw)
In-Reply-To: <42DF9E96.7050405@gmail.com>

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

  reply	other threads:[~2005-07-21 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 13:10 Andrew McCall
2005-07-21 16:56 ` Ian Lance Taylor [this message]
2005-07-22 10:50   ` Andrew McCall
2005-07-22 11:04     ` Rupert Wood
2005-07-22 12:27       ` Andrew McCall
2005-07-22 16:48     ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3pstcnln3.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=andrew.mccall@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).