News

Get the 1.26.0 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.25.0 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.25.0_rc2 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.25.0_rc1 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.24.0 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.24.0-rc3 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.24.0-rc2 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.24.0-rc1 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

With me (Alexey) being the only active maintainer, it is no longer possible to debug any issues arising on macOS systems. I do not have a macOS system, and Apple’s license does not allow one to install an image of macOS into a VM to do this kind of development work.

For the past couple of weeks I have been working on streamlining the handling of packages in crosstool-NG. Making all the packages handled consistently was the primary goal, since this will facilitate further changes, such as adding download validation, etc.

Get the 1.23.0 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.23.0.rc2 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Get the 1.23.0.rc1 release as bz2 (PGP signature) (md5, sha1, sha512) or xz (PGP signature) (md5, sha1, sha512) .

Well, this is kind of retroactive and old news, but I thought I needed to introduce myself.

Get the 1.22.0 release as bz2 (PGP signature) .

Get the 1.21.0 release as bz2 (PGP signature) .

I’m sure you’re probably still catching up on all the updates and call to arms on the list of patches in patchwork, but I have one more announcement to make.

Bryan Hundven has taken over as maintainer. Yann E. MORIN continues as a developer and stays on as an admin for site and release process.

Get the 1.20.0 release as bz2 (PGP signature) .

The server now has a new IP address, and should now be reachable again; just let the DNS caches expire, so the new address propagates. The root cause is as of yet unknown, but hopefully, this will not happen anymore. Thanks to the OSUOSL guys for their help in solving this issue!

It seems the crosstool-NG server is unreachable for some parts of the world. The issue is being investigated (update 2014-08-11: the configuration of the server is OK; there is a routing issue somewhere).

We now have a git tree! The Mercurial trees are now read-only, development will be done only on the git tree.

Get the 1.19.0 release as bz2 (md5, sha1, sha512) .

The mailing list is back to operational conditions! Thanks, and well done, sourceware.org! :-)

sourceware.org, which is hosting the crossgcc mailing list, is undergoing infrastructure overhaul, so the mailing list, and its archives, will be unreachable for a good part of the week. Sorry for the inconvenience. Stay tuned for more information.

Get the 1.18.0 release as bz2 (md5, sha1, sha512) .

Get the 1.17.0 release as bz2 (md5, sha1, sha512) .

The next release was due tonight. It’s gonna be late, by at least a few days… :-(

Get the 1.16.0 release as bz2 (md5, sha1, sha512) .

The next major release was due yesterday, but it is late. A few last-minute fixes to test, and it should be ready soon (expect before the week-end).

Get the 1.15.3 release as bz2 (md5, sha1, sha512) .

Get the 1.15.2 release as bz2 (md5, sha1, sha512) .

Get the 1.15.1 release as bz2 (md5, sha1, sha512) .

This release is broken! Do not use it!

Get the 1.15.0 release as bz2 (md5, sha1, sha512) .

Get the 1.13.3 release as bz2 (md5, sha1, sha512) .

This release is made specially for buildroot which is stuck to 1.13 in this cycle. If you are using crosstool-NG stand-alone, you would better upgrade to the 1.14 series.

Get the 1.14.1 release as bz2 (md5, sha1, sha512) .

Get the 1.14.0 release as bz2 (md5, sha1, sha512) .

Get the 1.13.3 release as bz2 (md5, sha1, sha512) .

Get the 1.13.2 release as bz2 (md5, sha1, sha512) .

Get the 1.13.1 release as bz2 (md5, sha1, sha512) .

Get the 1.13.0 release as bz2 (md5, sha1, sha512) .

Get the 1.12.4 release as bz2 (md5, sha1, sha512) .

Get the 1.12.3 release as bz2 (md5, sha1, sha512) .

Get the 1.12.2 release as bz2 (md5, sha1, sha512) .

This releases fixes the gdb version strings, see below.

Binutils and GDB have recently renamed their tarballs due to a GPL compliance issue, and the old tarballs are now missing. The binutils guys were kind enough to provide legacy symlinks so that scripts using the old versions continue to work; the issue has been reported here and here to gdb as well. This means that crosstool-NG releases so far choke when trying to download gdb. A fix to crosstool-NG to use the new versions is coming soon, but in the meantime, you’ll have to manually download the tarballs, and rename them to the old names.

Get the 1.12.1 release as bz2 (md5, sha1, sha512) .

Get the 1.12.0 release as bz2 (md5, sha1, sha512) .

Get the 1.11.4 release as bz2 (md5, sha1, sha512) .

Get the 1.11.3 release as bz2 (md5, sha1, sha512) .

Get the 1.11.2 release as bz2 (md5, sha1, sha512) .

Get the 1.11.1 release as bz2 (md5, sha1, sha512) .

Get the 1.11.0 release as bz2 (md5, sha1, sha512) .

Welcome!

Get the 1.10.1 release as bz2 (md5, sha1, sha512) .

I am pretty busy preparing the new server. Coding on crosstool-NG itself has slowed down in the meantime. Hopefully, all should be back to normal in the beginning of April 2011.

A few days ago (see the third entry, below), I wrote about a little surprise. In fact, I now own the crosstool-ng.org and crosstool-ng.net domains! :-) I will make them point to the new server as soon as I understand how DNS works… (they are parked for now…)

The OSUOSL has agreed to host the crosstool-NG project! Big thanks to them! I am working with them on setting up the VM that will be hosting the project. This means: better bandwidth, better availability, fixed IPv4 (v6 coming later), mailing lists, and so forth… If you have a few bucks in your pocket, please support OSUOSL for they are very helpful and dedicated to hosting FLOSS projects! And very soon, another little surprise… Shh… ;-)

Get the 1.9.3 release as bz2 (md5, sha1, sha512) .

Get the 1.10.0 release as bz2 (md5, sha1, sha512) .

Get the 1.9.2 release as bz2 (md5, sha1, sha512) .

Get the 1.9.1 release as bz2 (md5, sha1, sha512) .

Get the 1.9.0 release as bz2 (md5, sha1, sha512) .

Delaying the 1.9.0 release for a day, I did not have enough time to polish the tree because of ELC-E.

Get the 1.8.2 release as bz2 (md5, sha1, sha512) .

Get the 1.8.1 release as bz2 (md5, sha1, sha512) .

Get the 1.8.0 release as bz2 (md5, sha1, sha512) .

Get the 1.7.2 release as bz2 (md5, sha1, sha512) .

My talk on crosstool-NG has just been accepted for ELC-E 2010! :-) See you there, folks!

Get the 1.7.1 release as bz2 (md5, sha1, sha512) .

Get the 1.7.0 release as bz2 (md5, sha1, sha512) .

Get the 1.6.2 release as bz2 (md5, sha1, sha512) .

Get the 1.6.1 release as bz2 (md5, sha1, sha512) .

Get the 1.6.0 release as bz2 (md5, sha1, sha512) .

Get the 1.5.3 release as bz2 (md5, sha1, sha512) .

Get the 1.5.2 release as bz2 (md5, sha1, sha512) .

Get the 1.5.1 release as bz2 (md5, sha1, sha512) .

Get the 1.5.0 release as bz2 (md5, sha1, sha512) .

Update 2017-02-26 Mercurial repository is no longer used for ongoing development. For historical purposes, it is still available at [http://crosstool-ng.org/hg/crosstool-ng].

Get the 1.4.2 release as bz2 (md5, sha1, sha512) .

Update 2017-02-26 Mercurial repository is no longer used for ongoing development. For historical purposes, it is still available at [http://crosstool-ng.org/hg/crosstool-ng].

I’m experimenting with Mercurial to host the future development of crosstool-NG, and I’m setting up a new, upgraded server.

Get the 1.4.1 release as bz2 (md5, sha1, sha512) .

Get the 1.4.0 release as bz2 (md5, sha1, sha512) .

Get the 1.3.3 release as bz2 (md5, sha1, sha512) .

Get the 1.3.2 release as bz2 (md5, sha1, sha512) .

Get the 1.3.1 release as bz2 (md5, sha1, sha512) .

Get the 1.3.0 release as bz2 (md5, sha1, sha512) .

Get the 1.2.5 release as bz2 (md5, sha1, sha512) .

Get the 1.2.4 release as bz2 (md5, sha1, sha512) .

Get the 1.2.3 release as bz2 (md5, sha1, sha512) .

Get the 1.2.2 release as bz2 (md5, sha1, sha512) .

Get the 1.2.1 release as bz2 (md5, sha1, sha512) .

Get the 1.2.0 release as bz2 (md5, sha1, sha512) .

Get the 1.1.3a release as bz2 (md5, sha1, sha512) .

Get the 1.1.2 release as bz2 (md5, sha1, sha512) .

Get the 1.1.1 release as bz2 (md5, sha1, sha512) .

Get the 1.1.0 release as bz2 (md5, sha1, sha512) .

Welcome! :-)

Welcome on board, now a team of two! ;-)

Get the 1.0.0 release as bz2 (md5, sha1, sha512) .

Get the 0.3.2 release as bz2 (md5, sha1, sha512) .

Get the 0.3.1 release as bz2 (md5, sha1, sha512) .

Get the 0.3.0 release as bz2 (md5, sha1, sha512) .

Get the 0.2.2 release as bz2 (md5, sha1, sha512) .

Get the 0.2.1 release as bz2 (md5, sha1, sha512) .

Get the 0.2.0 release as bz2 (md5, sha1, sha512) .

Get the 0.1.2 release as bz2 (md5, sha1, sha512) .

Get the 0.1.1 release as bz2 (md5, sha1, sha512) .

Get the 0.1.0 release as bz2 (md5, sha1, sha512) .

Get the 0.0.4 release as bz2 (md5, sha1, sha512) .

Get the 0.0.3 release as bz2 (md5, sha1, sha512) .

Get the 0.0.2 release as bz2 (md5, sha1, sha512) .

Get the 0.0.1 release as bz2 (md5, sha1, sha512) .