[uClibc]mipsel ldd address 0x00000000?

[Jon Loeliger]

> >
> > But if I take it to the mipsel box, it continues to take
> > a segfault  if it is allowed to link at run time on the box.
> > (Other executable manage to do this just fine.)
> >
> > When I run ldd on the failing executable on the mipsel box,
> > it shows nothing.  If I run mispel-uclibc-ldd on the build
> > machine on the executable, it knows that libc (uClibc) needs
> > to be used, but states its address as 0x00000000.
> 
> It says 0x00000000 because you are doing a 'cross-ldd', which
> means that ldd cannot begin executing the shared lib loader to
> find out where it would be relocated to....
> 
> Nothing to worry about.

Excellent!

But then, should ldd on the box show where the load will happen
when not cross-ldd'ing?  It currently prints nothing.

Thanks!
jdl