|Summary:||ASTERISK-11713: Can not choose res_snmp in "make menuconfig" because dependency (net-snmp package) not recognized.|
|Date Opened:||2008-03-24 15:12:50||Date Closed:||2011-06-07 14:08:15|
|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.
****** ADDITIONAL INFORMATION ******
I tried to run ./configure with the --with-netsnmp=PATH parameter to no avail, but I must confess that I don't really know what PATH it needs.
I tried various paths that had net-snmp related files in them like /usr/bin, /usr/lib, and I would always get message at the end of ./configure that the netsnmp package was missing or corrupted.
|Comments:||By: Mark Michelson (mmichelson) 2008-03-24 15:23:11|
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.
By: joe_ (joe_) 2008-03-24 21:46:41
That did not help. The res_snmp module is still XXX'd out in "make menuconfig". I usually run "make clean" before rerunning "./configure". I'm not sure what you mean by "as long as it's used on your system". net-snmp is installed, but I'm not sure it's been set up to be used for anything. How would I check?
May I assume that others have compiled and installed this module without having this problem? If so, maybe I should try to find the packages from another source. This may not actually be an Asterisk bug, but if you think it might be, what else should I do to help track it down.
By: Donny Kavanagh (donnyk) 2008-03-25 13:48:54
This is a centos bug basically, previously your compile would of bombed, now due to ASTERISK-11508 we now check for a valid net-snmp environment, as a result because lm_sensors-devel is missing, the check fails. To resolve this issue:
yum install lm_sensors-devel
Let us know if that solves your issue and we can close the ticket.
By: joe_ (joe_) 2008-03-25 16:57:07
That did indeed solve my problem, but before you close and bury this issue, maybe there should be some notification of this put into the menuconfig interface or the README file. Explicitly listing an additional dependency can't hurt anyone but might help a lot of people who use Asterisk on CentOS.
By: Donny Kavanagh (donnyk) 2008-03-26 08:45:55
I'll check into it. And see if its possible.
By: Donny Kavanagh (donnyk) 2008-03-26 08:47:05
It is already noted in doc/snmp.txt however.
By: joe_ (joe_) 2008-03-26 19:32:42
Maybe it's just me, but I wouldn't normally think to look beyond the main installation directory for information relating to successfully selecting and compiling a module. I guess it comes down to how many of the people that will want to try to install this module do you think will go crying for help instead of looking for an answer in the doc directory or figuring out that they need to try to install the related -devel packages of all of the packages that are dependencies of the one package that you explicitly list as a dependency for a module. If you estimate the number to be very small, then by all means ignore them, do nothing and close the issue. Otherwise it may be justifiable to give them a bit more help. It's the developers' decision so I'll say no more whichever way it goes.
By: Donny Kavanagh (donnyk) 2008-03-26 20:12:50
I will see if we can get a note in the menuselect to check out doc/snmp.txt.
By: Jason Parker (jparker) 2008-03-27 16:40:27
Joe_, you are right in that many users probably won't look past the top level directory for documentation - but you'll see that if you do look, there is a README file which points to files in the doc/ directory for further information. There isn't a whole lot I can say about the users who didn't read the README file though...
In this particular case, we have explicitly listed all of the dependencies that we require. It is up to the distribution to properly package these dependencies. If we were to list absolutely everything required for a module, we would have to list some very low level components, which in many cases, would make the lists unreasonably long (imagine if we had to note that we require a C library for every single module..).