Bug 225308 - Broken librpm*.la shipped in /usr/lib64
Broken librpm*.la shipped in /usr/lib64
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Panu Matilainen
Depends On:
  Show dependency treegraph
Reported: 2007-01-29 16:15 EST by William A. Rowe, Jr.
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:39:01 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 William A. Rowe, Jr. 2007-01-29 16:15:59 EST
Reasonably stock, fresh RHES 3 Update 8 installation.

RHES 3.0 Update 8 Deployment Snafu, a discrepancy between the 32 and 64
bit libraries as shipped.  This specifically trips up netsnmp, but it's
likely to trip up any package that builds for 64 bits against librpm*.

Not an issue, but for reference; There are no /usr/lib/librpm*.la files.

There are four /usr/lib64/librpm*.la files.  Issue; these point to
dependency_libs including /usr/lib64/libbeecrypt.la

There is no .la file.  /usr/lib64/libbeecrypt.so and /usr/lib/libbeecrypt.so 
are missing, but /usr/lib64/libbeecrypt.so.6.1.0 and 
/usr/lib/libbeecrypt.so.6.1.0 and their .so.6 files are present.  

Most flavors of libtool are unable to resolve this situation.  No 
libbeecrypt.la exists, so libtool dies.  -lbeecrypt fails as well,
since the symlink for libbeecrypt.so (unnumbered) is missing.

By the time libtool is done failing to resolve these situations, it
falls back on /usr/lib/, which is altogether wrong for 64 bit compiles.

Unsure the root of the problem; is it the presence of the librpm.la
files?  Or the absence of libbeecrypt.la?  Or the absense of libbecrypt.so
and the mislinkage from librpm*.la to the libbecrypt.la?
Comment 1 RHEL Product and Program Management 2007-10-19 14:39:01 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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