From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: stable binutils, gcc, glibc ...
Date: Sat, 14 Oct 2000 05:55:50 +0200 [thread overview]
Message-ID: <20001014055550.B3816@bacchus.dhis.org> (raw)
In-Reply-To: <39E7EB73.9206D0DB@mvista.com>; from jsun@mvista.com on Fri, Oct 13, 2000 at 10:13:23PM -0700
On Fri, Oct 13, 2000 at 10:13:23PM -0700, Jun Sun wrote:
> Sorry to bring this topic again, but I cannot seem to sort out all the
> pieces of info together to get a consistent picture. Below is what I
> gathered through the recent emails on the lists. Please take a look and
> correct any mistakes. Particularly I like to know which version is
> considered STABLE today. Perhaps there is also issue what version works
> with what.
>
> Also, let me know if I miss something.
>
> In the end I like to put it on a web page and track the future toolchain
> developments - for lazy hackers. :-)
>
> Jun
>
> 1. binutils
> -----------
>
> a) latest binutil cvs tree (v2.10) + debian patch
>
> http://sourceware.cygnus.com/binutils/
> ftp://ftp.rfc822.org/pub/local/debian-mips/patches/rel32-binutils.diff
>
> b) Andreas Jaeger recommanded Ulf's patch against the CVS tree. He
> recommanded
>
> ftp://oss.sgi.com/pub/linux/mips/src/binutils/binutils-000420.diff.gz.
>
> But I only found the following file.
>
> ftp://oss.sgi.com/pub/linux/mips/binutils/binutils-000424.diff.gz
The binutils paragraph is old new. All of the required patches are now
in binutils except one which I sent to Ulf yesterday.
> c) What about those patches at the same ftp sites (v2.8.x)?
>
> ftp://oss.sgi.com/pub/linux/mips/binutils/
Still recommended because we can't yet be sure that binutils-cvs are
kosher yet. For example it's suspect that I can't build Emacs. Might
be something else but in case of doubt binutils are the suspect ...
> 2. gcc
> -------
>
> a) the cvs tree on oss.sgi.com (v2.7.2?) Any patch needed for TODAY's
> tree? Ralf seems to suggest his patch posted on 09/08 is still needed
> (constructor, Keith gcse, etc).
>
> b) Ralf's patch against egcs 1.1.2
>
> ftp://oss.sgi.com/pub/linux/mips/src/egcs/egcs-1.1.2.diff.gz
Only intended for mips64 kernels.. Almost guaranteed to be unusable for
anything else.
> c) Ralf's patch against egcs 1.0.3a. (Where is the base tar ball?)
On your favorite GNU site.
> ftp://oss.sgi.com/pub/linux/mips/egcs/egcs-1.0.3a-2.diff.gz
>
> d) Andreas said the current development version 2.96 worked - with the
> later binutils and gcc.
Plus above mentioned constructor patch.
Seems to work reasonably well.
> 3.glibc
> -------
>
> a) the cvs tree on oss.sgi.com (v2.0.6). Any patch needed?
No. However I'm not always doing the best job at keeping it uptodate.
> Florian pointed out the following patch. I am not 100% sure if it is
> aginst the current sgi CVS tree. Any confirmation?
>
> ftp://ftp.rfc822.org/pub/local/debian-mips/patches/rel32-glibc.diff
Against the glibc cvs tree at Cygnus.
> b) Andreas is trying to get glibc 2.2 working. Definitely bleeding edge
> stuff.
>
> http://www.suse.de/%7Eaj/glibc-mips.html
>
> c) Maciej reported he got binutils v2.10 working for glibc 2.2. No
> details or any distribution.
>
> d) glibc v2.0.7 from linux-vr project by Jay
>
> ftp://ftp.place.org/pub/nop/linuxce/
> ftp://ftp.place.org/pub/nop/linuxce/rpms/glibc-2.0.7-20.src.rpm
2.0.7 has resulted in so many bug reports that I consider to plain dump any
related reports in the future.
Ralf
next prev parent reply other threads:[~2000-10-14 3:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-14 5:13 stable binutils, gcc, glibc Jun Sun
2000-10-14 3:55 ` Ralf Baechle [this message]
2000-10-14 4:21 ` Ralf Baechle
2000-10-14 10:57 ` Florian Lohoff
2000-10-14 14:51 ` Jay Carlson
2000-10-14 14:51 ` Jay Carlson
2000-10-14 15:09 ` Ralf Baechle
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:29 ` Bradley D. LaRonde
2000-10-14 16:29 ` Bradley D. LaRonde
2000-10-16 0:35 ` Ralf Baechle
2000-10-16 1:33 ` Mike Klar
2000-10-16 1:33 ` Mike Klar
2000-10-16 11:26 ` Jay Carlson
2000-10-16 11:26 ` Jay Carlson
2000-10-16 11:30 ` Ralf Baechle
2000-10-16 12:00 ` Ralf Baechle
2000-10-18 1:59 ` Jay Carlson
2000-10-18 1:59 ` Jay Carlson
2000-10-18 20:31 ` Ralf Baechle
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:12 ` Ralf Baechle
2000-10-14 16:22 ` Bradley D. LaRonde
2000-10-14 16:22 ` Bradley D. LaRonde
2000-10-14 23:47 ` Keith Owens
2000-10-16 1:07 ` Ralf Baechle
2000-10-16 7:00 ` Alan Cox
2000-10-16 7:00 ` Alan Cox
2000-10-14 10:55 ` Florian Lohoff
2000-10-14 12:41 ` Ralf Baechle
[not found] ` <Pine.LNX.4.21.0010140730280.17430-100000@spawn.hockeyfiend.com>
2000-10-14 14:25 ` Ralf Baechle
2000-10-14 17:54 ` Florian Lohoff
2000-10-16 15:41 ` Maciej W. Rozycki
2000-10-18 4:04 ` The initial results (Re: " Jun Sun
2000-10-18 1:33 ` Florian Lohoff
2000-10-18 9:20 ` Jun Sun
2000-10-18 2:25 ` nick
2000-10-18 9:18 ` Florian Lohoff
2000-10-18 12:27 ` Ralf Baechle
2000-10-18 1:57 ` Ralf Baechle
2000-10-18 12:30 ` Florian Lohoff
2000-10-18 22:37 ` Ralf Baechle
2000-10-18 11:42 ` Geert Uytterhoeven
2000-10-18 17:15 ` Jun Sun
2000-10-20 14:55 ` Geert Uytterhoeven
2000-11-06 11:43 ` Jay Carlson
2000-11-06 11:43 ` Jay Carlson
2000-10-20 11:09 ` Andreas Jaeger
2000-10-20 12:03 ` Jay Carlson
2000-10-20 12:03 ` Jay Carlson
2000-10-21 1:24 ` Ralf Baechle
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=20001014055550.B3816@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jsun@mvista.com \
--cc=linux-mips@fnet.fr \
--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