Re: [ACTIVITY] weekly status
On 04/22/2012 11:58 PM, Michael Hope wrote: On 23 April 2012 00:54, Ken Werner wrote: Hi, * catching up with emails * rebased against current OE-core * OE is planning a release in april (following the yocto schedule) * noticed the libc of our binary toolchain is lacking i18n * caused a packaging issue for meta-linaro but easy to workaround * contents of the i18n folder are only used at runtime (not relevant for compiliation time) * updates in order to support for the 2012.03-20120326 binary toolchain * locations of sibgcc_s.so and libstdc++.so are different * added support for linaro gcc 2012.04 * looked at the meta-linaro patches made by Khem Which patches are these? Against the original meta-linaro or your new work in progress? Hi Michael, Khems branch lives at: https://github.com/kraj/meta-linaro/commits/master Two of them require a change to OE-Core that isn't upstream yet (due to the freeze) but can be found here: http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.7 Regards, Ken ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] April 16 - April 20
Hi, GDB for Android: * Wrote patch for bionic adding .note.ABI-tag to the crtbegin object files. Sent to Google engineers, They think it's going in the right direction and I will submit via gerrit. * Isolated Android-related changes in diff between AOSP's GDB 7.3.x and FSF GDB 7.3. There are a lot of unrelated changes there. * Sent e-mail asking for comments about the Android extension to .note.ABI-tag to the LSB and binutils mailing lists. Got only one e-mail of feedback. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ANNOUNCE] Linaro Toolchain Binaries 2012.04 released
The Linaro Toolchain Working Group is pleased to announce the 2012.04 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.7 2012.04 * Linaro GDB 7.4 2012.04 * 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: * Switches to the new GCC 4.7 based Linaro GCC * Adds native language support to most of the programs * Adds the mudflap, ssp, and gomp runtime libraries * Enables gnu_unique_object support in GCC Please see the README about running 4.7 based programs on a system with 4.6 based runtime libraries. The Linux version is supported on Ubuntu 10.04.3 and 11.10, 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/20yy.mm 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. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Cross testing applications under QEMU
We use QEMU to test programs built by the toolchain binary release for correctness. I've written up the instructions for spinning up your own at: https://wiki.linaro.org/MichaelHope/Sandbox/QEMUCrossTest It's focused on simplicity - getting a running, SSH only Cortex-A9 up and going as soon as possible. It's not the latest, not graphical, and doesn't replace the deeper documentation at: https://wiki.linaro.org/Resources/HowTo/Qemu -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross testing applications under QEMU
On 26 April 2012 02:39, Michael Hope wrote: > We use QEMU to test programs built by the toolchain binary release for > correctness. Is that really such a great idea? Qemu is generally less strict than actual hardware with things like alignment restrictions. This is fine for running software on a foreign architecture, which is the typical use case for emulators, and it is much faster than implementing strict checks for things no correct program should ever do. A few years ago, Codesourcery released an ARM compiler, binaries from which immediately crashed on real hardware. They had only tested the output in Qemu, never on hardware. Since then, many bugs in Qemu have been fixed, but I would still not trust it for validating a compiler. -- Mans Rullgard / mru ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross testing applications under QEMU
On 26 April 2012 13:58, Mans Rullgard wrote: > On 26 April 2012 02:39, Michael Hope wrote: >> We use QEMU to test programs built by the toolchain binary release for >> correctness. > > Is that really such a great idea? Qemu is generally less strict than > actual hardware with things like alignment restrictions. This is fine > for running software on a foreign architecture, which is the typical > use case for emulators, and it is much faster than implementing strict > checks for things no correct program should ever do. > > A few years ago, Codesourcery released an ARM compiler, binaries from > which immediately crashed on real hardware. They had only tested the > output in Qemu, never on hardware. Since then, many bugs in Qemu have > been fixed, but I would still not trust it for validating a compiler. Agreed, but this is more of a final validation and integration test. The same source tarball has been bootstrapped and a range of tests run on real hardware. This is testing that the later binary build builds programs and the programs run. QEMU is fine for a development test. On reflection, not for the final release test. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
