Bug 23781 - db2 interferes with db3 linking (severity = *fscking*stupid*)
db2 interferes with db3 linking (severity = *fscking*stupid*)
Product: Red Hat Linux
Classification: Retired
Component: perl (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-01-11 03:34 EST by j. alan eldridge
Modified: 2007-04-18 12:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-28 02:54:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description j. alan eldridge 2001-01-11 03:34:27 EST
I haven't got the exact logistics of this one traced down yet.

But, in a nutshell, trying to build perl from source with Berkeley DB
support doesn't work unless db2 is uninstalled. Otherwise, perl's little
test program gets db.h from db3 (ok so far), but  -ldb picks up libdb.so.3
-> libdb2.so.3, which, umm, doesn't work quite the way perl would like it
to. doesn't work the way I would like it to, either. ack! thppppxxxt!
Comment 1 Paul Lindner 2001-01-12 18:45:06 EST
Please fix this!

There is a solution for DB_File I've found.  The real root of this problem is
-L/lib -ldb  works for db3, whereas -L/usr/lib -ldb gives you db2.

You can modify the config.in file in the DB_File install to use /lib, and then
you're okay.

Otherwise this should be as simple as
ln -s /lib/libdb-3.1.so /usr/lib/libdb.so.4

or such....

Note You need to log in before you can comment on or make changes to this bug.