Hello,

I've just uploaded the tarballs for the latest oselas-toolchain stable
update. It's v2011.03.1 and can be downloaded here:
http://www.pengutronix.de/oselas/toolchain/download/

We now link the libelf statically into the toolchain, that should
increase portability of binary toolchains. Further I've fixed some
glibc-header problems seen on newer distributions.

You should use ptxdist-2011.03 to build the toolchain, but mol added
md5sum support so it might work with recent ptxdist, too (but you're on
your own if trying to do that :P).

No version changes for the linux based toolchains, tnx to Stephan Linz
for the avr updates.

here the complete shortlog:

Marc Kleine-Budde (3):
      glibc-header: fix directive .cfi_sections problem
      glibc-header: fix cpuid.h header problem
      scripts/make_release.sh: fix stable release with "v" sheme

Michael Olbrich (20):
      avrlib: add md5sum
      cross-binutils: add md5sum
      cross-ecj: add md5sum
      cross-gcc: add md5sum
      cross-gdb: add md5sum
      glibc-linuxthreads: add md5sum
      glibc-ports: add md5sum
      glibc: add md5sum
      host-gmp: add md5sum
      host-mpc: add md5sum
      host-mpfr: add md5sum
      host-zlib: add md5sum
      kernel-headers: add md5sum
      mingw-runtime: add md5sum
      newlib: add md5sum
      uclibc: add md5sum
      w32api: add md5sum
      host-libelf: new packages needed for gcc >= 4.5
      fixup_ptxconfigs.sh: OSELAS.Toolchain-2011.03.1
      ptxconfigs: update all configs

Stephan Linz (4):
      remove multilib configuration
      add Atmel AVR patches for 2.20.1
      add Atmel AVR patches for 4.4.3
      add new AVR toolchain

cheers, Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
ptxdist mailing list
[email protected]

Reply via email to