From: Bernardo Innocenti <bernie@develer.com>
To: uclinux-dev <uclinux-dev@uclinux.org>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
CrossGCC Mailing List <crossgcc@sources.redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] GCC 3.3.2/3.4 ColdFire toolchain for uClinux (20031103)
Date: Tue, 04 Nov 2003 23:27:36 +0100 [thread overview]
Message-ID: <3FA827D8.3000700@develer.com> (raw)
Hello,
I've released a new snapshot of the uClinux/ColdFire toolchain
based on GCC 3.3.2 and GCC 3.4-prerelease:
http://www.uclinux.org/pub/uClinux/uclinux-elf-tools/gcc-3/
This release incorporares quite a lot of updates and fixes
since the last official announcement.
Changes in release 20031102:
* Update GCC to 3.3.2 and 3.4-20031029;
* Update binutils to version 2.14.90.0.7;
* Finished integrating uClinux and ColdFire support in
official GCC and binutils. The 3.4 toolchain now builds
with no patches except for some pending GCC 3.4 bugfixes;
* Use self-extracting archives for all binary packages;
* Fix GCC 3.4 packaging problem (thanks to Frank Baumgart).
Changes in release 20031006:
* Most ColdFire and uClinux patches are now incorporated
in the official GCC 3.4 snapshots.
* Update GDB to 6.0, with new BDM patches.
* Update uClibc to 0.9.21.
* Enable pthreads support in uClibc (lightly tested).
* Split binary distribution in three packages (base, C++ and GDB).
* Several bugfixes all over the build script and patches.
Changes in release 20030811:
* Upgraded GCC 3.3.1 to the official release;
* Update links for GCC 3.4 to really point at the 20030806
snapshot.
Changes in release 20030808:
* uClibc multilibs for -msep-data were being built as
shared libraries (reported by Chen Qi).
* Update elf2flt from uClinux CVS and drop all patches.
* Update GCC 3.4 snapshot to 20030806. Fixes problems with -MD,
builds kernel, breaks libstdc++ multilibs (still investigating).
* Apply small fixes to GCC 3.4 patchset.
* Integrate GDB 5.3 with BDM support
* Restore building GCC 3.3.1 (got broken in previous release)
* Test with GCC 2.95.3: surprisingly, it still builds fine...
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
reply other threads:[~2003-11-04 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FA827D8.3000700@develer.com \
--to=bernie@develer.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.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