On Mon, Apr 03, 2000 at 10:33:00PM -0700, NJ Verenini wrote:
... 
> The chain of events goes something like this:
> 
> 1) build process makes some shared objects, puts them in a temporary
> directory (say .libs)
> 2) executables are linked against those shared objects in the temporary
> directory
> 3) installation installs bin and libs in their usual places
> 4) when trying to run bin, loader tries to get library from .libs,
> -instead- of looking in LD_LIBRARY_PATH
> 
> The problem, of course, is that you are likely to no longer be in the
> build directory, so the loader reports it can't find the shared object.
> 
> I looked at some of the software with the problem (how it built
> executables), and they all seem to do something like this:
> 
> gcc .libs/libfoo.so -o foo foo.c
> 
> instead of something like
> 
> gcc -o foo foo.c -L./libs -lfoo
> 
> Maybe that is part of the problem...

That in general is all of the problem with configure/libtool these days!
The work around for me (thanks to Bob Friesenhahn) is

configure --disable-fast-install

not obvious...

Cheers,

Patrick