Try setting LIBPATH on AIX rather than LD_LIBRARY_PATH. (I usually
don't use gcc on AIX, only xlc, so I'm not positive that advice is
going to help, but it may be worth a try.)
-Travis
On Mar 5, 2004, at 6:32 PM, paulb@burnside.powells.com wrote:
>
>> Not finding BDB at runtime is a common problem, adding
>> /path/to/bdb/lib to LD_LIBRARY_PATH might fix it. I assume the
>> regression tests (i.e. make check) also fail?
>
> That didn't make any difference. As far as make check goes it looks
> like
> it fails immediately due to a lack of Python on this box.
>
>> It's not really a serious error as far as install is concerned, you
>> could ignore it, but if it also affects the installed binaries then
>> you have a real problem.
>
> It looks like all the binaries in the installed bin directory give the
> same missing libdb message.
>
>>> If I copy libdb.so to /usr/lib then instead it complains about libz
>>> and
>>> some libgcc stuff being missing.
>>
>> Do you have libz in a non-standard location? It could be a libtool
>> problem since the 1.0.0 tarball mistakenly shipped with a non-standard
>> libtool. If you have libtool and autoconf installed you could run
>> autogen.sh in the source directory, then configure and make.
>
> It's in /usr/local/lib which I guess isn't standard for aix. But if I
> move
> it into /usr/lib then I still get some oddball messages about libgcc*
> libraries being missing. I'm certain they do not belong in /usr/lib.
>
> I might try grabbing libtool and autoconf.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 6 01:53:37 2004