Looking more at this, I don't think the problem has
anything to do with Swish-e -- the machine is borked.
I'll get back to the list if I find there's a real
--- Bill Moseley <email@example.com> wrote:
> On Sat, Dec 20, 2003 at 04:42:58AM -0800, J Robinson
> > --- Bill Moseley <firstname.lastname@example.org> wrote:
> > > On Fri, Dec 19, 2003 at 07:34:38AM -0800, J
> > > wrote:
> > >
> > > >
> > > error
> > > > in loading shared libraries:
> > >
> > > What's ldd lt-swish-e show?
> > >
> > # find . -name lt-swish-e
> > ./src/.libs/lt-swish-e
> > # ldd `find . -name lt-swish-e`
> > libxml2.so.2 =>
> /usr/local/lib/libxml2.so.2 (0x40015000)
> > libpthread.so.0 =>
> > libswish-e.so.2 =>
> /usr/local/lib/libswish-e.so.2 (0x4010a000)
> > libz.so.1 => /usr/lib/libz.so.1
> > libm.so.6 => /lib/libm.so.6 (0x4108d000)
> > libc.so.6 => /lib/libc.so.6 (0x410aa000)
> > /lib/ld-linux.so.2 => /lib/ld-linux.so.2
> Doesn't look like things are broken. Try some
> debugging. Try running
> that src/.libs/lt-swish-e program or
> src/.libs/swish-e. Also try
> running the src/swsih-e script. That script is a
> wrapper that allows
> running the program before it is installed -- i.e.
> before libraries are
> installed in their final locations and are still in
> the source tree.
> You can also run any of those with strace -e
> trace=open to watch the
> paths search for libraries. You might need to use
> -f to follow forked
> processes, but I'm not sure if -f is available on
> all systems.
> Bill Moseley
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
Received on Sat Dec 20 17:20:37 2003