Wheels, reinventing. (Was Re: [uClibc] Understanding what the build wrapper does...)

Erik Andersen andersen at codepoet.org
Thu Sep 11 11:10:15 UTC 2003


On Fri Sep 05, 2003 at 03:56:34PM -0400, Rob Landley wrote:
> It's 2201 bytes dynamically linked, and I put it in the chroot root_fs thingy 
> and it actually ran, too!

:-)

> BUT: to do it, I had to create a symlink in the mounted root_fs:
> cd $DIR/lib
> ln -s libc.so.0 libc.so
> 
> I don't know why I needed to do this, I just know that this is what ld was 
> looking for when I told it "--library-path $DIR/lib -lc".  It wouldn't look 
> at the "libc.so.0" version, it wanted "libc.so"

The symlinks are needed to allow shared libraries to be 
easily upgraded in-place.

> Am I missing something?  Should that symlink already have been there?  Is my 
> copy of ld broken or something?  (Red Hat 9 stock compiler toybox...)

The uClibc 'make install' command (and all the variants on that
theme such as 'make install_runtime') do in fact install such a
symlink....  Perhaps you just copied things rather than using
i.e. 'make install_runtime'?

> I'm confused, but this is actually normal for me...

heh.  :-)

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



More information about the uClibc mailing list