Bug 79046 - libgdbm.la includes incorrect libdir
libgdbm.la includes incorrect libdir
Product: Red Hat Linux
Classification: Retired
Component: gdbm (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeff Johnson
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2002-12-04 20:05 EST by Jeffrey Hutzelman
Modified: 2015-01-07 19:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-23 07:56:19 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 Jeffrey Hutzelman 2002-12-04 20:05:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.17 i686)

Description of problem:
gdbm-devel contains /usr/lib/libgdbm.la which specifies libdir='/usr/local/lib',
but the libraries are actually in /usr/lib.
This causes libtool-using programs which need libgdbm to fail to link, and also
poisons dependencies in .la files built for other libtool-using libraries.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
# grep libdir /usr/lib/libgdbm.la

# rpm --query -f /usr/lib/libgdbm.la

# rpm --verify gdbm-devel
(produces no output, indicating the files are as shipped)

Additional info:

Workaround is to edit /usr/lib/libgdbm.la, changing libdir to /usr/lib. 
Naturally, this must be done on every machine.  Because this problem affects .la
files generated when building other libtool-using libraries which link against
libgdbm, and because it does _not_ affect linking programs which do not use
libtool, it may be difficult to recognize that a fix is needed.

An appropriate solution to this problem would be to fix the build process so
that an incorrect libgdbm.la is not installed.
Comment 1 Jeff Johnson 2004-08-23 07:56:19 EDT
Current gdbm-devel-1.8.0-24 contains

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