[uClibc] libgcc_s.so.1

John Ronan jronan at tssg.org
Wed May 25 15:08:47 UTC 2005


Hi,

Many thanks for taking the time to reply.

On 25 May 2005, at 11:09, Joakim Tjernlund wrote:

>>
>> Morning,
>>
>> I'd been working away quite happily with uClibc until last thursday
>> someone accidentally reformatted my build machine.  As I had backups I
>> though that I could just re-install the machine, install uClibc and
>> buildroot as before (uClibc 0.9.27, buildroot-20050520).  After
>> recompiling everything and trying to boot the target system I get a
>> library not found error on libgcc_s.so.1.  Doing a 'strings' on the
>> binary shows that its there, but it used not be there.
>>
>> My point I suppose is, have I done something wrong (again)? or should 
>> I
>> could copy libgcc_s.so.1 into /lib on the target machine?  I'm going 
>> to
>
> Nope, no copy should be needed.

Mmmm.. I'm not sure I understand.
Before the machine got hosed, it was SuSE 9.1, now its Debian testing 
(if that helps any)

Anyhow, I copied the dropbear binary into the toolchain filesystem to 
do an ldd and I got (Debian Host)
ilnacullin:/src# ldd dropbear
ldd: can't open cache '/etc/ld.so.cache'
         libutil.so.0 => /lib/libutil.so.0 (0x40007000)
         libcrypt.so.0 => /lib/libcrypt.so.0 (0x40009000)
         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4001d000)
         libc.so.0 => /lib/libc.so.0 (0x40023000)
         ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40000000)

The previous dropbear binary gives the following (SuSE host)
ilnacullin:/src# ldd dropbearold
ldd: can't open cache '/etc/ld.so.cache'
         libutil.so.0 => /lib/libutil.so.0 (0x40007000)
         libcrypt.so.0 => /lib/libcrypt.so.0 (0x40009000)
         libc.so.0 => /lib/libc.so.0 (0x4001d000)
         ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40000000)

Previously I just had copied all the libs from /usr/i386-linux-uclibc/ 
(generated by compiling uClibc itself ) onto my targets filesystem and 
it worked fine, now I've broken it.

The newly compiled dropbear runs fine in the toolchain, so I'm assuming 
that its library structure is correct.  Should I now copy the '/lib' 
directory from the toolchain to my targets filesystem? Could this be 
what I should have been doing all along and I was just lucky 
(blissfully ignorant even)?

Regards
John

--
John Ronan <jronan at tssg dot org>, +353-51-302938
Telecommunications Software &  Systems Group,  http://www.tssg.org




More information about the uClibc mailing list