Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 58782 - bad libdir entries in .la files
bad libdir entries in .la files
Product: Red Hat Linux
Classification: Retired
Component: ucd-snmp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Knirsch
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-01-24 09:17 EST by rm0
Modified: 2015-03-04 20:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-24 09:17:08 EST
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 rm0 2002-01-24 09:17:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.7) Gecko/20011221

Description of problem:
The files 

(included in the ucd-snmp-devel sub-package) contain 


entries. If you recompile the ucd-snmp packages you obtain

libdir='<your rpm build root>/usr/lib'

I think It's a bug but I'm not sure if it harms.

I found this when I was 'stracing' snmpd
and saw several lines where the daemon is trying
unsuccessfuly to open() files
like '/var/tmp/ucd-snmp/usr/lib/i686/mmx/libucdmibs...'

(I was using a locally rebuilt source rpm package)

Maybe these open attempts are signs of another different  

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

How reproducible:

Steps to Reproduce:
1. $ rpm -q ucd-snmpd-devel
2. $ cat /usr/lib/libsnmp.la

Actual Results:  The libdir entries in the 
have wrong paths.

Expected Results:  The libdir entries in the 
files should have the '/usr/lib' value

Additional info:

The newest RHL 6.2 errata packages for ucd-snmp
(4.2.1-4.6.x) suffer from the same problem.
Comment 1 Phil Knirsch 2002-01-29 10:30:27 EST
The latest version (4.2.3) is available via rawhide now. This should fix this


Read ya, Phil

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