From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] 001117 toolchain release
Date: Sat, 18 Nov 2000 05:34:58 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205748@msgid-missing> (raw)
I have put a new toolchain on ftp.cygnus.com in pub/ia64-linux/snap-001117.
This fixes all significant known toolchain problems. I don't expect to be
adding more patches to the toolchain unless another serious toolchain bug is
found.
There is one more significant ABI change since the last release. There was
a corresponding glibc change, so this requires an up-to-date glibc (Nov 16 or
later). If you already have glibc 2.2, you need to recompile from scratch.
If you are trying to use this toolchain with glibc 2.1.3, then you need a
new copy of the README.glibc213 file, since this file now needs to revert 3 ABI
changes instead of 2. Since there are no public OS distributions using glibc
2.2 yet, the glibc and toolchain maintainers decided it was better to fix ABI
bugs now than later.
I expect that the next toolchain release will be something based off of the
FSF gcc 3.0 tree sometime early next year. This depends on when gcc 3.0 will
be available, and that is anybody's guess, but the general idea here is to get
all of us migrated to an official FSF release instead of the development
releases that we have been using.
Jim
next reply other threads:[~2000-11-18 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 5:34 Jim Wilson [this message]
2000-11-21 5:47 ` [Linux-ia64] 001117 toolchain release Keith Owens
2000-11-22 2:18 ` Jim Wilson
2000-11-22 2:33 ` Keith Owens
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=marc-linux-ia64-105590678205748@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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