[asterisk-bugs] [Asterisk 0012290]: Can not choose res_snmp in "make menuconfig" because dependency (net-snmp package) not recognized.

[noreply at bugs.digium.com]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=12290 
====================================================================== 
Reported By:                Joe_
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12290
Category:                   Resources/res_snmp
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta5 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 89511 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-24-2008 15:12 CDT
Last Modified:              03-24-2008 15:23 CDT
====================================================================== 
Summary:                    Can not choose res_snmp in "make menuconfig" because
dependency (net-snmp package) not recognized.
Description: 
The res_snmp module can not be chosen in "make menuconfig" apparently
because the net-snmp installation isn't recognized.  It says in "make
menuconfig" that it depends on "netsnmp".  Could this be because of
confusion about the naming of the net-snmp/netsnmp package, or are these
two different pieces of software.  Even within the package itself both
names seem to be used

I am running on a Trixbox 2.6 installation which uses CentOS 5.1 
"yum list net-snmp*"  shows that I have net-snmp, net-snmp-devel,
net-snmp-libs and net-snmp-utils all installed.  It could perhaps be
possible that the Trixbox developers did something wrong/nonstandard in
creating the net-snmp package.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 03-24-08 15:23  
---------------------------------------------------------------------- 
By using the package, you don't need to specify a path when running
configure. An important step that you may have left out is `make distclean`
prior to running the configure script. Try this prior to re-running the
configure script and see if this clears up the problem. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-24-08 15:23  putnopvut      Note Added: 0084459                          
03-24-08 15:23  putnopvut      Status                   new => feedback     
======================================================================