[uClibc]mipsel ldd address 0x00000000?

[Erik Andersen]

On Wed Jun 18, 2003 at 03:28:52PM -0700, Jon Loeliger wrote:
> >         ld-uClibc.so.0 => /usr/mipsel-linux-uclibc/lib/ld-uClibc.so.0
> > (0x0x2aaa8000)
> > $ ./hello
> > hello world
> 
> So, I see lines _like_ those on the build box, but with zero addresses.
> (Nice 0x0x in there, btw! :-)  The actual paths are hard coded paths
> relative to the build environment and toolset that I just built.

Yipe!  Good spotting on the '0x0x'!  I guess the likelyhood of
seeing an obvious bug is inversely proportional to the number of
times you have looked at it.  I've looked at the output about a
zillion times, and never even noticed the double '0x'.

    <fixing>

All fixed up now, thanks.

> Like:
> 
> %
> /localstore0/jdl/mumble/vbs/build_mipsel/staging_dir/bin/mipsel-uclibc-l
> dd /tmp/jdl/div
>         libc.so.0 =>
> /localstore0/jdl/mumble/vbs/build_mipsel/staging_dir/lib/libc.so.0
> (0x00000000)
>         /lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)

> But on the mipsel target box, ldd is totally silent.

This typically means that it was unable to execute the shared lib
loader...  On my mipsel system I have a symlink from
/lib/ld-uClibc.so.0 to where uClibc's shared lib loader resides.

i.e. in your case, as root you would do:
    
    cd /lib
    ln -s /localstore0/jdl/mumble/vbs/build_mipsel/staging_dir/lib/ld-uClibc.so.0

and then you should get some nice non 0x00000000 addresses,

 -Erik

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