Bug 103982 - net-snmp-devel is missing rpm dependancies
Summary: net-snmp-devel is missing rpm dependancies
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-snmp
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-08 19:36 UTC by Steve Grubb
Modified: 2015-03-05 01:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-17 08:36:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Grubb 2003-09-08 19:36:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
While trying to compile php 4.3.2, it would fail in configure when testing the
snmp library. This was entered in bugzilla #103388 against php. The problem is
php's configure tests the static snmp library which requires the libelf.a
library. The static libelf library is kept in libelf-devel. Therefore, anyone
that has netsnmp-devel installed also must have libelf-devel installed or static
compilations may fail.

The maintainer of php said I should open this bug report so that net-snmp-devel
can get the libelf-devel requirement added to the spec file.

Version-Release number of selected component (if applicable):
net-snmp-devel-5.0.6-17

How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh php-4.3.2-2.src.rpm
2. rpmbuild -bb /usr/src/redhat/SPEC/php.spec

    

Actual Results:  The rpm build fails in sanity check of snmp.

Expected Results:  Php successfully compiled.

Additional info:

This issue is also in the RH 8.0 library. All libraries need updating in case a
security issue causes everyone to upgrade packages.

Comment 1 Joe Orton 2003-10-12 20:17:57 UTC
This bug is still present in Fedora Core Beta 2.

Comment 2 Phil Knirsch 2003-10-17 08:36:18 UTC
Fixed in net-snmp-5.0.9-2 and later.

Read ya, Phil


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