Noticed people downloading only target toolchains. No - that does not work without host toolchain.

Some toolchains for embedded development may be downloaded in here.

Toolchains are for our internal use, but may freely be used by others too.

Supported host systems: these toolchains work basicly with any Linux distributions: no external shared libraries used, currently only i686 executables.

Notice: binutils used with GCC 4.1.2 is exprerimental 2.17.50+ cvs snapshot. Waiting for binutils 2.18...

Toolchains are constructed continuously, so check the real versions [here].

We do not have sources available here, because you may download all the sources throught following links.

Notice some toolchains contain extra tools for which location of sources are within howto documents.

• More C libraries for toolchains: dietlibc (already present for rootfs), newlib, open_solaris, uclibc (done, needs testing)
  (bold meaning under work)

• To change all toolchain target runtime libraries location to directory $BASEDIR/ROOT/lib. Symlinks from old location $BASEDIR/lib.
  Why? ROOT directory itself may be copied to target's installation root. Clean and simple.
• To add AVR32 + newlib toolchain. This way to newlib toolchains.
• jnc (Java Native Compiler) toolchain.
• ARM Cortex toolchain (LM3S101).
• gdb in every toolchain.
• More development tools.
  dwarfdump & libdwarf |
• To have automatically generated product description containing configuration options, possibly also test case outputs.
• To construct toolchain/ROOT which contains libraries etc. for target root fs. Naturally toolchain/lib contains symlinks to shared libraries in toolchain/ROOT/lib.
• To change the structure to its own loop mountable filesystem(?)
• To distribute also as qemu volume.

• java support
  SDK, JRE, phoneme, etc. support is going to be within distributions.

Please inform us (using contact form) if there's inexpensive (embedded) cpu board(s) available. Maybe we'll construct toolchain for it.