The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.07 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build.
Uses include: * Cross compiling ARM applications from your laptop * Remote debugging * Build the Linux kernel for your board
What's included: * Linaro GCC 4.8 2013.07-1 * Linaro Newlib 2.0 2013.06 * Linaro Binutils 2.23 2013.06 * Linaro Eglibc 2.17-2013.07-2 * Linaro GDB 7.6 2013.05 * A statically linked gdbserver * A system root * Manuals under share/doc/
The system root contains the basic header files and libraries to link your programs against.
Interesting changes include: * The sysroot is based on Linaro versions of Eglibc. About details of Linaro Eglibc, please refer https://releases.linaro.org/13.07/components/toolchain/eglibc-linaro.
The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian 6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and later, and should run on any Linux Standard Base 3.0 compatible distribution. Please see the README about running on x86_64 hosts.
The Windows version is supported on Windows XP Pro SP3, Windows Vista Business SP2, and Windows 7 Pro SP1.
The binaries and build scripts are available from: https://launchpad.net/linaro-toolchain-binaries/trunk/2013.07
Need help? Ask a question on https://ask.linaro.org/
Already on Launchpad? Submit a bug at https://bugs.launchpad.net/linaro-toolchain-binaries
On IRC? See us on #linaro on Freenode.
Other ways that you can contact us or get involved are listed at https://wiki.linaro.org/GettingInvolved.
Know issues: * Some version information in README are incorrect. * gdb can not backtrace into libc.
Notes: * To use all of the features of Linaro eglibc, the sysroot in 32-bit toolchain release is updated to Linaro eglibc, which is 2.17. If you get runtime errors about libc version, please get the sysroot from the release tarball (gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/) or download from launchpad
https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro-...
If you do not want to use Linaro sysroot, you'd add option to gcc to find your sysroot:
--sysroot=<directory>
* To run 32-bit application built from arm-linux-gnueabihf toolchain in aarch64 system, you'd copy sysroot and runtime from release package to your root of aarch64 system. i,e.
scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/arm-linux-gnueabihf/libc/* AARCH64-SYSTEM:/ scp -r gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_runtime/* AARCH64-SYSTEM:/
2013-07-30 10:01 GMT+08:00 Zhenqiang Chen zhenqiang.chen@linaro.org:
The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.07 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build.
Uses include:
- Cross compiling ARM applications from your laptop
- Remote debugging
- Build the Linux kernel for your board
What's included:
- Linaro GCC 4.8 2013.07-1
- Linaro Newlib 2.0 2013.06
- Linaro Binutils 2.23 2013.06
- Linaro Eglibc 2.17-2013.07-2
So the libraries search path has been moved from /lib /usr/lib to /lib/arm-linux-gnueabihf/ and /usr//lib/arm-linux-gnueabihf/? i want to know the rule for that. if people want to be compatible with old buildsystem, so we suppose we use a LD_LIBRARY_PATH?
- Linaro GDB 7.6 2013.05
- A statically linked gdbserver
- A system root
- Manuals under share/doc/
-barry
linaro-toolchain@lists.linaro.org