Thanks, everyone, for the help. I've successfully configured and built
httpd 2.0.48, now.
The Subversion installation documentation talks about ld.so.conf in the
context of Subversion, but not Apache/Berkeley DB, as far as I can tell.
It should probably indicate that the ld.so.conf modifications need to be
made for https 2.0.48 to find Berkeley DB 4.2.
It should probably made clear as well that the correct entry to
ld.so.conf is /usr/local/BerkeleyDB.4.2/lib, not /usr/local/BerkeleyDB.4.2 .
Cheers,
Garret
Sander Striker wrote:
> The reason you didn't 'need' the LDFLAGS=-R... or LD_LIBRARY_PATH=.. (or
> select other options), is because the old logic didn't check if the db
> it found for linking was the correct version. It would detect the db4
> header file and detect it could link to some version of db (in /usr/lib
> for instance). The new code checks to see if it can actually link to
> the version of db that has the same version as was being looked for.
> Hence the need for being able to resolve the path to the library at
> runtime.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 29 17:47:05 2003