Ben Collins-Sussman <sussman@collab.net> writes:
> I feel your pain. This pain has been hounding me for years. It seems
> that different versions of BDB simply *cannot* coexist on one box, and
> as a result, every OS has implemented its own custom solution to the
> problem (renaming libraries, installing them in weird places, etc.)
> It makes our ./configure system hellish.
Sure they can. The problem is that everyone tries to cram
everything into the same prefix, or even if they do use different
prefixes they configure the linker to search them all by default.
Install each db version into its own prefix (this is the default
for a good reason). Then, configure each app only to search the
lib dir for the appropriate version of db at build and run time,
with the appropriate combination of -L and -Wl,-R or
LD_LIBRARY_PATH settings. I know it's popular on GNU/Linux to
muck about with ld.so.conf, but that brings you back to
effectively having them all in the same prefix.
UNIX shared library implementations give you plenty of rope with
which to hang yourself. Be careful. And stay away from
precompiled packages.
--
Eric Gillespie <*> epg@pretzelnet.org
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 17 00:06:13 2003