From: ralf@uni-koblenz.de
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Binutils 2.9.x
Date: Mon, 9 Nov 1998 14:03:41 +0100 [thread overview]
Message-ID: <19981109140341.D541@uni-koblenz.de> (raw)
I've been asked if I recommend an upgrade to binutils 2.9.x when I recently
posted patches. No, at this time I even disrecommend an upgrade since
binutils 2.9.1.0.4 have been the most buggy binutils version I touched since
a long, long time. Rebuilding glibc 2.0.99 triggers more than 3000 lines
warning messages for failed assertions in elf32-mips.c, I get core dumps and
all sorts of sick effects.
I touched them though for two reasons. First of all, in the interest of
getting an Linux distribution working for us with as little changes as
possible we should go with whatever the Linux distributor uses. In case
of Redhat 5.1 this is binutils 2.9.1.0.4. Second I've started to work a bit
on glibc 2.0.99. In order to get symbol versioning working we need at
least binutils 2.9.1.
Ralf
next reply other threads:[~1998-11-11 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-09 13:03 ralf [this message]
[not found] ` <E0zdX1R-0003xm-00@fountain.nexus.co.uk>
1998-11-11 23:31 ` Binutils 2.9.x ralf
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=19981109140341.D541@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.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