From: Pete Popov <ppopov@embeddedalley.com>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: does someone succeed in making the toolchain for 2.6 kernel?
Date: Wed, 21 Dec 2005 00:57:12 -0800 [thread overview]
Message-ID: <1135155432.9009.18.camel@localhost.localdomain> (raw)
In-Reply-To: <50c9a2250512210051q85f813fx27b0533fe66165e2@mail.gmail.com>
On Wed, 2005-12-21 at 16:51 +0800, zhuzhenhua wrote:
> i want to compile a 2.6.14 kernel for mips 4kec, does someone compile
> the 2.6 kernel with self-build toolchain?
Quite a few people have, I'm sure.
> how to select the gcc,
> gdb,glibc,linux head and binutils version?
> and where to get the guide doc?
If you have such questions, I would suggest you start by compiling and
booting your kernel with a toolchain and distribution that already
works. Build your own toolchain, if you must, later.
Pete
next prev parent reply other threads:[~2005-12-21 8:56 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
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 [this message]
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=1135155432.9009.18.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=linux-mips@linux-mips.org \
--cc=zzh.hust@gmail.com \
/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