From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Trouble building cross compilers
Date: Thu, 21 Mar 2002 10:28:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905312@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905309@msgid-missing>
Jesse Barnes <jbarnes@sgi.com> writes:
|> a) built and installed binutils 2.12 (configured with
|> --target=ia64-gnu-linux --prefix=/tmp/ia64-cross-3.0)
|> b) tried to build and install gcc 3.0 (configured with the same options
|> as above), but with 'make LANGUAGES=c' instead of just 'make'
LANGUAGES=c is obsolete, configure with --enable-languages=c instead.
|> Unfortunately, I got hung up in the middle of step (b) with the errors
|> shown below. IIRC, the Cygnus snapshot tarballs were 'cross-compile
|> ready' in that they had all the necessary header files and utilities
|> needed for a full cross development environment. Any notes on how
|> those trees were built would be appreciated.
You need to have the target headers installed somewhere and use
--with-headers=/place/of/target/headers when configuring the cross
compiler.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-03-21 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 2:30 [Linux-ia64] Trouble building cross compilers Jesse Barnes
2002-03-21 10:28 ` Andreas Schwab [this message]
2002-03-21 20:02 ` Steve Christiansen
2002-03-21 20:48 ` Jim Wilson
2002-03-21 21:01 ` Jim Wilson
2002-03-22 0:28 ` Jesse Barnes
2002-03-22 0:57 ` Keith Owens
2002-03-22 1:02 ` Jesse Barnes
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=marc-linux-ia64-105590701905312@msgid-missing \
--to=schwab@suse.de \
--cc=linux-ia64@vger.kernel.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