From: Erik Mullinix <Hesp@rainworks.org>
To: Phil Thompson <Phil.Thompson@pace.co.uk>, linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain
Date: Wed, 21 Mar 2001 07:11:46 -0500 [thread overview]
Message-ID: <001a01c0b200$1c13d5e0$0500a8c0@shaft> (raw)
In-Reply-To: 1402C4C025C4D311B50D00508B8B74E281B14D@exchange1
What Error's are you getting?
Hesp
----- Original Message -----
From: "Phil Thompson" <Phil.Thompson@pace.co.uk>
To: <linux-mips@oss.sgi.com>
Sent: Wednesday, March 21, 2001 9:00 AM
Subject: RE: Recommended toolchain
> So, going back to the original question, what are the recommended
versions -
> particularly if you are building 2.4.x kernels?
>
> Are the recomendations in the HOWTO out of date? I had to patch va-mips.h
> from the egcs RPM and more fixes seem to be needed before I get a kernel
> that compiles.
>
> Thanks,
> Phil
>
> -----Original Message-----
> From: Ralf Baechle [mailto:ralf@oss.sgi.com]
> Sent: 20 March 2001 20:37
> To: Karel van Houten
> Cc: simong@oz.agile.tv; linux-mips@oss.sgi.com
> Subject: Re: Recommended toolchain
>
>
> On Tue, Mar 20, 2001 at 09:12:02PM +0100, Karel van Houten wrote:
>
> > You wrote:
> > > Recently I've been working with various version mixes of the gnu tool
> > > chain for a mipsel-linux target and settled on a patchy binutils
> > > 2.8.1/egcs 1.1.2/glibc 2.0.6 setup. However this lacks the
functionality
> > > that I would get from a newer toolchain for use with the linux 2.4
> > > kernel. As a result, I was wondering if someone could recommend the
> > > latest "stable"/recommended toolchain for a mipsel-linux target.
> >
> > Well, I'm currently using:
> > binutils 2.10.1
> > gcc 2.95.3 (with Maciej's patches)
> > glibc 2.2.2 (compiled with above toolchain).
> >
> > This toolchain works for native compiles on my mipsel box.
> > One drawback: I can't compile any kernels with this setup,
> > For kernel compiles I use 2.8.1/egcs-2.90.27/glibc-2.0.6.
>
> You MUST use minimum egcs-2.91.66 (1.1.2); older compilers WILL
misscompile
> kernels.
>
> Ralf
>
next prev parent reply other threads:[~2001-03-21 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 14:00 Recommended toolchain Phil Thompson
2001-03-21 12:11 ` Erik Mullinix [this message]
2001-03-21 16:06 ` Keith M Wesolowski
-- strict thread matches above, loose matches on Subject: below --
2003-04-10 19:23 recommended toolchain carbonated beverage
2001-03-22 9:39 Recommended toolchain Phil Thompson
2001-03-22 9:43 ` Geert Uytterhoeven
2001-03-21 18:46 Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski
2001-03-22 7:49 ` Geert Uytterhoeven
2001-03-20 3:06 Simon Gee
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:37 ` Ralf Baechle
2001-03-20 20:37 ` Ralf Baechle
2001-03-27 19:02 ` Maciej W. Rozycki
2001-03-29 17:28 ` Houten K.H.C. van (Karel)
2001-03-29 17:28 ` Houten K.H.C. van (Karel)
2001-03-29 17:39 ` Karel van Houten
2001-03-29 17:39 ` Karel van Houten
2001-03-29 18:10 ` Maciej W. Rozycki
2001-04-01 14:39 ` Houten K.H.C. van (Karel)
2001-04-01 18:54 ` Florian Lohoff
2001-03-29 17:51 ` Maciej W. Rozycki
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='001a01c0b200$1c13d5e0$0500a8c0@shaft' \
--to=hesp@rainworks.org \
--cc=Phil.Thompson@pace.co.uk \
--cc=linux-mips@oss.sgi.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