RE: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server
Hi Michael, I've a new question about the installation of linaro toolchain. Why linaro toolchain need lsb? How does the toolchain uses lsb? I'm now trying to use the prebuilt toolchain in Ubuntu 9.04. After I install lsb, linaro toolchain can work. But my old gcc4.3.3 toolchain can't work now. r65388@bluejay:~$ ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -bash: ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: No such file or directory r65388@bluejay:~$ LD_DEBUG=libs /lib32/ld-linux.so.2 ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: error while loading shared libraries: ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: cannot open shared object file: No such file or directory It seems difficult to fully remove lsb. Thus I want to know how the prebuilt toolchain uses lsb. Thanks~~ Yours Terry -Original Message- From: Michael Hope [mailto:michael.h...@linaro.org] Sent: 2012年1月12日 7:28 To: Lv Terry-R65388 Cc: linaro-toolchain@lists.linaro.org Subject: Re: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server On Wed, Jan 11, 2012 at 11:56 PM, Lv Terry-R65388 wrote: > Hi Michael, > > I changed the symbol link of /lib/ld-linux.so.2. > > sudo ln -s -f /lib32/ld-linux.so.2 /lib/ld-linux.so.2 > > But it seems the problem is still not resolved. > > r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib > -2011.12/arm-fsl-linux-gnueabi/bin$ ls -la /lib/ld* lrwxrwxrwx 1 root > root 20 2012-01-11 15:42 /lib/ld-linux.so.2 -> /lib32/ld-linux.so.2 > r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib > -2011.12/arm-fsl-linux-gnueabi/bin$ ./arm-linux-gnueabi-gcc > -bash: ./arm-linux-gnueabi-gcc: No such file or directory > > I'll check the server again. Hi Terry. I couldn't reproduce the problem on a fresh install of Ubuntu 11.10 x86_64 Server. I started with a clean install and saw similar to your problem: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc -bash: ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc: No such file or directory I then installed lsb using `sudo apt-get install lsb`. This changed the error to one about missing the 32 bit libstdc++: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory I then installed the 32 bit libraries using `sudo apt-get install ia32-libs`. The binary then works: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc arm-linux-gnueabi-gcc: fatal error: no input files For reference, here's the linkers afterwards: cbuild@crucis-oneiric:~$ ls -la /lib/ld* lrwxrwxrwx 1 root root 25 2011-10-05 11:07 /lib/ld-linux.so.2 -> i386-linux-gnu/ld-2.13.so lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.1 -> ld-linux.so.2 lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.2 -> ld-linux.so.2 lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.3 -> ld-linux.so.2 cbuild@crucis-oneiric:~$ ls -la /lib/i386-linux-gnu/ld* -rwxr-xr-x 1 root root 126152 2011-10-05 11:07 /lib/i386-linux-gnu/ld-2.13.so lrwxrwxrwx 1 root root 10 2011-10-05 11:07 /lib/i386-linux-gnu/ld-linux.so.2 -> ld-2.13.so From our tests yesterday you have the linker and all of the libraries needed to run the problem. The error message from bash is probably due to a broken symlink. I recommend you look into that futher. Good luck and let me know if I can help! -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
RE: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server
Hi Michael, It my fault. The issue is fixed. Typo error. Sorry for that. Thanks~~ Yours Terry -Original Message- From: linaro-toolchain-boun...@lists.linaro.org [mailto:linaro-toolchain-boun...@lists.linaro.org] On Behalf Of Lv Terry-R65388 Sent: 2012年2月27日 17:29 To: Michael Hope Cc: linaro-toolchain@lists.linaro.org Subject: RE: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server Hi Michael, I've a new question about the installation of linaro toolchain. Why linaro toolchain need lsb? How does the toolchain uses lsb? I'm now trying to use the prebuilt toolchain in Ubuntu 9.04. After I install lsb, linaro toolchain can work. But my old gcc4.3.3 toolchain can't work now. r65388@bluejay:~$ ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -bash: ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: No such file or directory r65388@bluejay:~$ LD_DEBUG=libs /lib32/ld-linux.so.2 ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: error while loading shared libraries: ./gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc: cannot open shared object file: No such file or directory It seems difficult to fully remove lsb. Thus I want to know how the prebuilt toolchain uses lsb. Thanks~~ Yours Terry -Original Message- From: Michael Hope [mailto:michael.h...@linaro.org] Sent: 2012年1月12日 7:28 To: Lv Terry-R65388 Cc: linaro-toolchain@lists.linaro.org Subject: Re: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server On Wed, Jan 11, 2012 at 11:56 PM, Lv Terry-R65388 wrote: > Hi Michael, > > I changed the symbol link of /lib/ld-linux.so.2. > > sudo ln -s -f /lib32/ld-linux.so.2 /lib/ld-linux.so.2 > > But it seems the problem is still not resolved. > > r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib > -2011.12/arm-fsl-linux-gnueabi/bin$ ls -la /lib/ld* lrwxrwxrwx 1 root > root 20 2012-01-11 15:42 /lib/ld-linux.so.2 -> /lib32/ld-linux.so.2 > r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib > -2011.12/arm-fsl-linux-gnueabi/bin$ ./arm-linux-gnueabi-gcc > -bash: ./arm-linux-gnueabi-gcc: No such file or directory > > I'll check the server again. Hi Terry. I couldn't reproduce the problem on a fresh install of Ubuntu 11.10 x86_64 Server. I started with a clean install and saw similar to your problem: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc -bash: ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc: No such file or directory I then installed lsb using `sudo apt-get install lsb`. This changed the error to one about missing the 32 bit libstdc++: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory I then installed the 32 bit libraries using `sudo apt-get install ia32-libs`. The binary then works: cbuild@crucis-oneiric:~$ ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc arm-linux-gnueabi-gcc: fatal error: no input files For reference, here's the linkers afterwards: cbuild@crucis-oneiric:~$ ls -la /lib/ld* lrwxrwxrwx 1 root root 25 2011-10-05 11:07 /lib/ld-linux.so.2 -> i386-linux-gnu/ld-2.13.so lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.1 -> ld-linux.so.2 lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.2 -> ld-linux.so.2 lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.3 -> ld-linux.so.2 cbuild@crucis-oneiric:~$ ls -la /lib/i386-linux-gnu/ld* -rwxr-xr-x 1 root root 126152 2011-10-05 11:07 /lib/i386-linux-gnu/ld-2.13.so lrwxrwxrwx 1 root root 10 2011-10-05 11:07 /lib/i386-linux-gnu/ld-linux.so.2 -> ld-2.13.so From our tests yesterday you have the linker and all of the libraries needed to run the problem. The error message from bash is probably due to a broken symlink. I recommend you look into that futher. Good luck and let me know if I can help! -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 20th - 24th February
Investigated and produced and patch for bug lp936863. Continued work on 64-bit shifts. I updated my neon shifts patch twice: once to take -Os optimization into account, and once because I noticed that the CC clobbers were being retained even after they were known to be not required, and presumably this could be a bad thing. Posted a patch to improve SI->DImode sign- and zero-extends that also move values from core registers to neon registers. Wrote a patch to implement negation in neon register, albeit at the cost of a scratch register to hold the constant zero. This worked, but insisted on loading the zero from memory, despite the fact that NEON has a suitable instruction for loading zero. Attempted to get "vmov dN, #0" to work. The problem appears to be that DImode loads are handled by the VFP load pattern in vfp.md and that that doesn't seem to DTRT for integer constants. I've got as far as trying to figure out what it does do, but there's more to be done to get to the bottom of the problem. Tried to get the benchmarking going for 64-bit shifts. Unfortunately ursa1 has been experiencing outages. Michael has been trying to fix it, but so far I've not been able to run anything there. Instead, I've launched benchmark runs via Michael's normal test infrastructure. Hopefully this can replace the manual ones anyway. That would be more convenient. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Feb 20 - Feb 24
Hi, GDB on Android: * Set up cross compiling environment using both the Android toolchain and the Linaro toolchain. * Tested Android and Mozilla GDB running as a native binary on the Linaro Android image on qemu. None of them were able to see all threads in a multi-threaded process. The same happens with a native binary on Android talking to a gdbserver on localhost. * I was able to produce an Android GDB 7.1.x binary which when running on an i386 host talking to the Android SDK emulator sees all threads. It is not able to generate a backtrace though. * Carnival holidays. -- []'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
Cards
Hi Ken, Thiago. Could you try your hand at writing cards for the OpenEmbedded Core meta-layer and GDB and Android? Here are some past cards: https://linaro-public.papyrs.com/TCWG2011-GCC-O3 https://linaro-public.papyrs.com/TCWG2011-OPENOCD-SUPPORT https://linaro-public.papyrs.com/TCWG2011-WINDOWS-TOOLCHAIN They cover: * An introduction * The why/advantages * The what/features * The how/steps * Dependencies * Acceptance criteria (which is a post-tense version of the body) A card should cover three calendar months. Check the unknowns - we need to investigate the acceptance criteria and make sure there is no unexpected side work in there. We use roadmap cards as the highest level of organising our work. Cards are the interface between working groups and the TSC and sit at the project brief / deep but concise level. Draft them on the wiki (cf https://wiki.linaro.org/KenWerner/Sandbox) and we'll go from there. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Running benchmark variants
Here's brief notes on running different benchmark variants across the auto builders. Asa, could you pull these plus your notes into a wiki page? Spawn a job: http://ex.seabright.co.nz/helpers/scheduler/spawn Merge requests are automatically built. Otherwise, drop arbitrary tarballs into cbuild@orion:~/snapshots and spawn . For example, scp gcc-4.6.3.tar.gz cbuild@orion:~/snapshots; spawn gcc-4.6.3 into a9-builder. Jobs: * gcc-version - build and test GCC * benchmarks-gcc-version - run coremark, denbench, eembc against the already built version * benchmarks-spec2000-gcc-version - run spec2000 Queues: * a9-builders: anything that can naive build a A9 compiler * a9-ref: reference A9 boards * a8-ref: reference A8 boards Variables: * BENCHMARKS = list, such as coremark spec2000 pybench - run these benchmarks instead of the defaults Variants: * By default we build o3-neon * See http://bazaar.launchpad.net/~linaro-toolchain-dev/cbuild/trunk/view/head:/lib/all-variants.mk for all names * Spawn a job with VARIANT_SRC = all and VARIANT_LIST = glob-pattern Examples: * VARIANT_LIST = o3-neon o3-vfpv3 (compare NEON with VFPv3D32) * VARIANT_LIST = o3-neon-cortexa8 o3-neon-cortexa9 (compare -mtune=cortexa8 vs -mtune=cortexa9( * VARIANT_LIST = o3-neon-novect o3-neon (compare with/without the vectoriser) -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Saturated operations
Hi Ulrich. The saturated work you're doing at the moment - is it the saturated add/subtract QADD/QSUB/QDADD/QDSUB or the ARMv6 saturate-word-with-shift SSAT/USAT? I've updated the old blueprint and added a new one for SSAT/USAT: https://blueprints.launchpad.net/gcc-linaro/+spec/armv6-saturation-instructions https://blueprints.launchpad.net/gcc-linaro/+spec/armv5-saturated-ops and was wondering which to put against your name. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Fleshing out the QEMU blueprints
Hi Peter, Rusty. I've fleshed out the KVM blueprints a bit more at: https://wiki.linaro.org/MichaelHope/Sandbox/Q1.12ToDo Notable is adding validation and de-PENDING a few things. I need to know the following things before talking to Validation and Platforms about things that are in their queue: * What's the host kernel? Christoffers, or a linux-linaro-kvm based off his plus work in progress? * What's the guest kernel? * Anything special that needs to be in the host rootfs outside qemu and libvirt? Do you have a host and guest kernel .config that I can pass on to Platforms? -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
