In message <200209112337.g8BNbcG12627@buzzard.buzzard.freeserve.co.uk> you wrote:

> 
> > > Also, you should still be able to use ldd on the executable.  For example, 
> > > one a.out legacy binary I have reports:
> > > 
> > > $ ldd gdb
> > > gdb:
> > >         -ltermlib.0 => /emul/aout//usr/lib/libtermlib.so.0.5 (0x2018f000)
> > >         -lm.0 => /emul/aout//usr/lib/libm.so.0.1 (0x20192000)
> > >         -lc.12 => /emul/aout//usr/lib/libc.so.12.81 (0x201b7000)
> > > 
> > 
> > I get the following result:
> > 
> > netwinder-rm: {21} ldd /usr/pkg/bin/ncftp2
> > /usr/pkg/bin/ncftp2:
> >         -lposix.0 => not found (0x0)
> >         -lc.12 => /usr/lib/libc.so.12.62.1 (0x2004c000)
> > 
> 
> What does 
> 
> 	file /usr/lib/libc.so.12.62.1
> 
> report?  If it is an a.out shared lib, then maybe it is confusing the emul 
> search.  If it is, then try moving it to the emul subtree (12.62 sounds 
> very old for an elf shared library).
> 
> R.

Now I identified the problem: 

Because of my somehow chaotic upgrade procedure I had both the a.out and the 
elf libraries in /usr/lib and also in /emul/aout/usr/lib.

This indeed confused the system. I fetched the old libraries from fresh 
from my NetBSD 1.5.2 box (Shark) and put it in /emul/aout/usr/lib.

And it works.   :-))

Thank to all for the helpful hints!


Stefan

-- 
-----------------------------------------------------------------------------
Stefan Wuerthner                             web  http://wuerthner.dyndns.org
-----------------------------------------------------------------------------