Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: does someone succeed in making the toolchain for 2.6 kernel?
Date: Wed, 21 Dec 2005 09:55:39 +0100	[thread overview]
Message-ID: <20051221085539.GS13985@lug-owl.de> (raw)
In-Reply-To: <50c9a2250512210051q85f813fx27b0533fe66165e2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

On Wed, 2005-12-21 16:51:35 +0800, zhuzhenhua <zzh.hust@gmail.com> wrote:
> i want to compile a 2.6.14 kernel for mips 4kec, does someone compile
> the 2.6 kernel with self-build toolchain? how to select the gcc,
> gdb,glibc,linux head and binutils version?
> and where to get the guide doc?

After you've built your toolchain, it's either an additional native
one (gcc-4.1), or you've build some kind of cross-toolchain that got a
prefix (mips-linux-gcc).

In the former case, you'd be able to "make CC=gcc-4.1" a kernel, in
the later case you call make like "make CROSS_COMPILE=vax-linux-".

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 für einen Freien Staat voll Freier Bürger"  | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-21  8:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  8:51 does someone succeed in making the toolchain for 2.6 kernel? zhuzhenhua
2005-12-21  8:55 ` Jan-Benedict Glaw [this message]
2005-12-21  9:04   ` zhuzhenhua
2005-12-21  9:18     ` Jan-Benedict Glaw
2005-12-21 10:02       ` Matej Kupljen
2005-12-21 10:06         ` Jan-Benedict Glaw
2005-12-21 10:32           ` Matej Kupljen
2005-12-21 10:37             ` zhuzhenhua
2005-12-22  2:43             ` zhuzhenhua
2005-12-22  8:57               ` Jan-Benedict Glaw
2005-12-22  9:05                 ` zhuzhenhua
2005-12-22  9:23               ` Matej Kupljen
2005-12-22  9:30                 ` zhuzhenhua
2005-12-22  9:46                   ` Matej Kupljen
2005-12-22 13:29               ` Stephen P. Becker
2005-12-23  4:46                 ` zhuzhenhua
2005-12-21 10:27       ` P. Christeas
2005-12-21  8:57 ` Pete Popov
2005-12-21  9:06   ` zhuzhenhua
2005-12-21  9:22     ` Jan-Benedict Glaw
2005-12-21 19:00       ` Ralf Baechle
2005-12-21 20:29         ` Jan-Benedict Glaw
2005-12-21  9:47     ` Kevin D. Kissell
2005-12-21  9:47       ` Kevin D. Kissell

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=20051221085539.GS13985@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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