From: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
To: simong@oz.agile.tv (Simon Gee)
Cc: linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain
Date: Tue, 20 Mar 2001 21:12:02 +0100 (MET) [thread overview]
Message-ID: <200103202012.VAA07412@sparta.research.kpn.com> (raw)
In-Reply-To: <3AB6C948.7F8EE4B7@oz.agile.tv>
Hi Simon,
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.
--
Karel van Houten
----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer.
----------------------------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
To: Simon Gee <simong@oz.agile.tv>
Cc: linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain
Date: Tue, 20 Mar 2001 21:12:02 +0100 (MET) [thread overview]
Message-ID: <200103202012.VAA07412@sparta.research.kpn.com> (raw)
Message-ID: <20010320201202.KPyq_Ok_EBEMHSGxmhuohL1CwN59neXoKE7Sy9PEPhE@z> (raw)
In-Reply-To: <3AB6C948.7F8EE4B7@oz.agile.tv>
Hi Simon,
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.
--
Karel van Houten
----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer.
----------------------------------------------------------
next prev parent reply other threads:[~2001-03-20 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 3:06 Recommended toolchain Simon Gee
2001-03-20 20:12 ` Karel van Houten [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 14:00 Phil Thompson
2001-03-21 12:11 ` Erik Mullinix
2001-03-21 16:06 ` Keith M Wesolowski
2001-03-21 18:46 Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski
2001-03-22 7:49 ` Geert Uytterhoeven
2001-03-22 9:39 Phil Thompson
2001-03-22 9:43 ` Geert Uytterhoeven
2003-04-10 19:23 recommended toolchain carbonated beverage
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=200103202012.VAA07412@sparta.research.kpn.com \
--to=k.h.c.vanhouten@research.kpn.com \
--cc=linux-mips@oss.sgi.com \
--cc=simong@oz.agile.tv \
/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