[ACTIVITY] 18th - 22nd January
Port to microinstance - TCWG-432 [2/10] * More fallout from attempts to fix race condition * Began cleaning job submission YAML Controlled image builds - TCWG-360 [1/10] * (Re)learned how to generate images from hwpack + filesystem Struck down by flu [7/10] ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 04
o Teaching activity (3/10) == Progress == o Infra/Validation (1/10) * A couple of patches for release script. o GCC dev. (2/10) * Remote testing sanitizing: still digging. o Misc (4/10) * Various meetings (usual ones and internal ones) * Backports reviews == Plan == o Continue on GCC testsuite and opened cards. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 25th - 29th January
Port to microinstance - TCWG-432 [4/10] * Went a few more rounds with the race condition, finally nailed it * Tidied up transfer of Coremark results to LAVA * Added metadata to LAVA results * Sketched some charts using LAVA reporting * Improved runtime benchmark logging Benchmarking infrastructure documentation - TCWG-496 [2/10] * Most everything drafted, some docs finished Controlled image builds - TCWG-360 [2/10] * Reached a better understanding of what a hwpack is * Generated a few images, none of them booted Misc [2/10] =Plan= Benchmarking-102 slides for Connect Finish documentation Backport benchmarking If builder shows up in microinstance, evaluate stability of its Junos ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: armhf toolchain with glibc 2.13
On Sat, Jan 30, 2016 at 5:35 AM, Aaron R wrote: > My ARM target runs glibc 2.13 and I am having a hard time finding a > linaro toolchain for it. It seems like all the ones I have found ship with > glibc 2.15 (even old ones). If you link statically, most code compiled against a newer glibc is likely to work. One potential problem is that a newer glibc might call a newer kernel syscall entry point, which may not exist in your kernel if you have an old one, but this is likely to be a rare problem. And of course anything that requires dynamic linking won't work if statically linked, but this is usually only a problem for large and complex programs. > Where can I find the binaries for a linux toolchain that targets armhf > with glibc 2.13? It looks like we have some very old releases that used eglibc-2.13 http://releases.linaro.org/archive/12.03/components/toolchain/binaries/ This was only tested on 4 year old linux versions which are obsolete, and is so old that we don't support it anymore. This being one of the very first binary toolchain releases from Linaro, I have no idea how well it works. You may be better off if you build one yourself. If you can copy files off of your target, then create a target sysroot containing /lib, /usr/lib, and /usr/include. Put a copy of this target sysroot on your cross compiler host. Then configure binutils and gcc using --with-sysroot= pointing at the path to the target sysroot. You only need to build binutils and gcc, and you need to configure, build, and install binutils before doing the same for gcc. You can get the target gcc configure options by using gcc -v on the target, then adjust the options so that they make sense on the cross compiler build system, e.g. don't use --prefix=/usr as you should not install the cross compiler into /usr on the build system. Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 25-29 January 2016
== Progress == - Public Holiday (2/10) - LTO and TCWG480 (4/10) * Started with a prototype for VRP * Experimenting with simple test cases - Misc (4/10) * gcc/bug list * LTO and Undefined behaviors slides for connect * Meetings == Plan == * LTO * bugs ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 25 - 29 January 2016
== Progress == LLDB development -- Submitted patch fixing return value handling on arm-linux-gnueabihf [TCWG-228] [5/10] -- float and double types handled in above patch did some more investigation for handling structs [TCWG-228] [2/10] -- Collecting LLDB status data, ran testsuite on different hardware and minor investigation of fails and xfails [2/10] Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB development -- Update float/double return value patch after review and commit upstream -- Submit a fix for handling structs as return types on arm-linux-gnueabihf Public Holiday -- Friday 5th February 2016 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
