Bug 42335 - unresolved symbols from rpmlib when building w/ ucd-snmp 4.2-12
Summary: unresolved symbols from rpmlib when building w/ ucd-snmp 4.2-12
Status: CLOSED DUPLICATE of bug 41452
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ucd-snmp   
(Show other bugs)
Version: 7.1
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Brock Organ
URL: http://net-snmp.sourceforge.net/tutor...
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-25 21:02 UTC by Scott Leerssen
Modified: 2015-03-05 01:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-25 21:02:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Scott Leerssen 2001-05-25 21:02:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
It appears that the ucd-snmp package was not built on a 7.1 system.  When I
build the sources from the net-snmp site (referenced URL), I get a whole
bunch of unresolved symbols when the ustMain program builds.  If I get the
sources for ucd-snmp, the configure script compensates for the missing
symbols, which leads me to believe that an older system was used to build
the rpm.  Note also that this problem does not occur on a 7.0 system, which
again, leads me to believe that the rpm was built on a non-vanilla 7.1

One more note: the unresolved symbols occur only with the shared library
libucdmibs.so.  If I link against the .a file, all is well.

How reproducible:

Steps to Reproduce:
1.download the sources from the aforementioned URL

Actual Results:  lots of undefined references to rpmlib functions

Expected Results:  build with no failures

Additional info:

Comment 1 Phil Knirsch 2001-06-05 19:45:06 UTC

*** This bug has been marked as a duplicate of 41452 ***

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