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 <r65...@freescale.com> 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
