From: Matej Kupljen <matej.kupljen@ultra.si>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-mips@linux-mips.org
Subject: Re: does someone succeed in making the toolchain for 2.6 kernel?
Date: Wed, 21 Dec 2005 11:32:16 +0100 [thread overview]
Message-ID: <1135161136.5211.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20051221100619.GW13985@lug-owl.de>
Hi
> > Yes, we use crosstool, but the results matrix isn't rely
> > encouraging:
> > http://www.kegel.com/crosstool/crosstool-0.38/buildlogs/
>
> Well, try do do it any better *yourself*. Compiling a complete
> toolchain (incl. userland support) really isn't easy...
You probably misunderstood me :(
I was trying to say, that we use crosstool *successfully* to build
kernel 2.6.15-rc5 (and a bunch of user land binaries) and that
this matrix should be updated.
If someone looks at this matrix, he thinks that for mips(el) crosstool
does not work.
BR,
Matej
next prev parent reply other threads:[~2005-12-21 10:31 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 [this message]
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=1135161136.5211.8.camel@localhost.localdomain \
--to=matej.kupljen@ultra.si \
--cc=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