Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@optushome.com.au>
To: linux-mips@linux-mips.org
Subject: Re: Trouble compiling MIPS cross-compiler
Date: Sun, 18 Jan 2004 18:04:31 +1000	[thread overview]
Message-ID: <200401181804.31114@korath> (raw)
In-Reply-To: <400A3353.6050903@gentoo.org>

> 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.

Oh ok then - so what should I do to actually compile a MIPS kernel?  I'd 
rather not have to download an entirely separate kernel source, so should I 
just go back to gcc-3.1.1 that supports -mcpu?

Will kernel 2.6.1 or whatever's next work properly in this respect?  I realise 
that there are plenty of valid reasons for removing -mcpu, but it does create 
a big headache for us users, who just want the darn thing to 'go' ;-)

> You'll also want to pass something like this:
> make ARCH=mips CROSS_COMPILE=mips-unknown-linux-gnu- <target>

Oh ok - yes, I sort of guessed how to do this as it wasn't written anywhere, 
and I used "mips-linux" for everything so all should be well there.

At any rate, I think I'll have to call it a day - it's way too much of a 
hassle just to get a working MIPS cross-compiler, and with all the hoops you 
have to jump through I haven't got any patience left :-(

Thanks for all your help everyone,
Adam.

  parent reply	other threads:[~2004-01-18  8:04 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
2004-01-18  7:17                 ` Eric Christopher
2004-01-18  8:04                 ` Adam Nielsen [this message]
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=200401181804.31114@korath \
    --to=a.nielsen@optushome.com.au \
    --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