From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: Trouble compiling MIPS cross-compiler
Date: Sun, 18 Jan 2004 02:18:43 -0500 [thread overview]
Message-ID: <400A3353.6050903@gentoo.org> (raw)
In-Reply-To: <200401181646.04740@korath>
Adam Nielsen wrote:
> Thanks for all the info! Well, I tried building gcc-3.3.2 with your options
> and that worked (hooray!) but I couldn't find binutils-2.14.90.0.7, the
> closest I could see was 2.14 so I used that. It all compiled ok, but now
> when I go to compile the kernel I get this error:
>
> cc1: error: invalid option `cpu=r3000'
http://www.kernel.org/pub/linux/devel/binutils/
The 2.14.90.0.X series of binutils is a linux-only release maintained by
HJ Lu, while the 2.14 version is more or less the official GNU version.
As for the kernel, -mcpu was deprecated in gcc-3.2.x, and totally
removed in gcc-3.3.x. You'll want to use the -march option (or
-mips[1234] as a synonym), although if you use a recent kernel source
tree off linux-mips anoncvs, selecting the right CPU/Machinetype in
menuconfig will supply the proper -march/-mipsX commands to the
compiler. You'll also want to pass something like this:
make ARCH=mips CROSS_COMPILE=mips-unknown-linux-gnu- <target>
Note: CROSS_COMPILE needs to be set to the CHOST the cross compiler was
built with, in my cases, I use the extended CHOST form. The more common
form is mips[el]-linux (or mips64[el]-linux)
For 2.4, if you want a mips64 kernel, pass ARCH=mips64. For 2.6, pass
ARCH=mips and select 64-bit mode in menuconfig (or oldconfig or xconfig)
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
next prev parent reply other threads:[~2004-01-18 7:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 7:11 Trouble compiling MIPS cross-compiler Adam Nielsen
2004-01-17 7:36 ` Adam Nielsen
2004-01-17 16:27 ` Thiemo Seufer
2004-01-17 16:35 ` Ralf Baechle
2004-01-17 16:33 ` Ralf Baechle
2004-01-18 1:19 ` Adam Nielsen
2004-01-18 1:54 ` Adam Nielsen
2004-01-18 3:46 ` Ralf Baechle
2004-01-18 4:14 ` Eric Christopher
2004-01-18 5:10 ` Adam Nielsen
2004-01-18 5:31 ` Eric Christopher
2004-01-18 5:36 ` Kumba
2004-01-18 6:46 ` Adam Nielsen
2004-01-18 6:56 ` Eric Christopher
2004-01-18 7:28 ` Thiemo Seufer
2004-01-18 7:35 ` Unscribe this maillist ??(zhufeng)
2004-01-18 7:35 ` ??(zhufeng)
2004-01-18 19:41 ` Trouble compiling MIPS cross-compiler Eric Christopher
2004-01-18 7:18 ` Kumba [this message]
2004-01-18 7:17 ` Eric Christopher
2004-01-18 8:04 ` Adam Nielsen
2004-01-18 8:13 ` Kumba
2004-01-18 10:05 ` Geert Uytterhoeven
2004-01-22 2:32 ` Solving the cross-compiler issue (Was: Trouble compiling MIPS cross-compiler) Nathan Field
2004-01-22 20:12 ` Daniel Jacobowitz
2004-01-22 20:32 ` Kumba
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=400A3353.6050903@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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