| 1 |
Hi. I recently faced (probably well-known) problem while setting up my embedded |
| 2 |
/usr/arm-module3-linux-gnueabi system tree. The problem is that |
| 3 |
/lib/libgcc_s.so does not exist. Here is typical error message: |
| 4 |
|
| 5 |
~ # bash |
| 6 |
bash: error while loading shared libraries: libgcc_s.so.1: cannot open |
| 7 |
shared object file: No such file or directory |
| 8 |
|
| 9 |
I know that there is a workaround - copying this lib from |
| 10 |
/usr/lib/gcc/.. to /usr/lib (paths are relative to arm's root). Also, |
| 11 |
manual [1] suggests installing gcc on target system and using host's |
| 12 |
gcc-config. I tried it and failed. My actions were: |
| 13 |
|
| 14 |
emerge-arm-module3-linux-gnueabi gcc |
| 15 |
ROOT=/usr/arm-module3-linux-gnueabi gcc-config -l |
| 16 |
|
| 17 |
I looked inside host's gcc-config. Looks like it only works with |
| 18 |
NATIVE compiler's libgcc_s.so. It treats arm's gcc as cross-compiler |
| 19 |
despite the fact that arm's gcc is actually native for arm system. |
| 20 |
Well, I install gcc-config on arm. It turns out, that gcc-config |
| 21 |
depends on libgcc_s itself. |
| 22 |
|
| 23 |
~ # gcc-config |
| 24 |
/bin/bash: error while loading shared libraries: libgcc_s.so.1: cannot |
| 25 |
open shared object file: No such file or directory |
| 26 |
|
| 27 |
Funny. Should I mail gcc-config bug? |
| 28 |
|
| 29 |
Sergey. |
| 30 |
|
| 31 |
[1] http://gentoo.mindzoo.de/index.cgi/wiki/Cross%20Install |
| 32 |
[2] http://www.gossamer-threads.com/lists/gentoo/amd64/190796 |
Archives