Skip to contentSkip to conversation

net-snmp config help

meta-oe Jack Mitchell 1 participant 3 messages Jul 2, 2012 – Jul 4, 2012

lore
Share & tools
lore
#0 lore raw

Ok, so I managed to get net-snmp compiling however I now have an issue where the configure stage is picking up libpci and using that to configure net-snmp to look for pci devices on startup which my beaglebone doesn't have

   root@beaglebone:~# snmpd
   pcilib: Cannot open /proc/bus/pci
   pcilib: Cannot find any working access method.
   root@beaglebone:~#

Off I went and found a solution[1] which states that I should force the PCI_* defines to off *after* the configuration stage. So I go into my work directory and alter includes/net-snmp/net-snmp-config.h:

/* define if you have pci_lookup_name() */
#undef HAVE_PCI_LOOKUP_NAME

/* Define to 1 if you have the <pci/pci.h> header file. */ #undef HAVE_PCI_PCI_H

Then compile with:

bitbake net-snmp -c compile -f

Then

bitbake core-image-minimal

Which does net-snmp do_install and then builds the rootfs. However this makes no difference and it still fails with the same error message on start. Is my work flow for this wrong, or is it re-configuring, I'm at a bit of a loss of what to do now?

I suppose the correct procedure would be to find out why pcilibs is being detected and configured, then fix that. Could anyone point me in the right direction?

Regards,
Jack.

[1] http://stackoverflow.com/questions/9470494/snmpd-cannot-open-proc-bus-pci

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  http://www.embed.me.uk

--
#1 lore raw
Quoted 23 lines · Jack Mitchell

Ok, so I managed to get net-snmp compiling however I now have an issue where the configure stage is picking up libpci and using that to configure net-snmp to look for pci devices on startup which my beaglebone doesn't have

   root@beaglebone:~# snmpd
   pcilib: Cannot open /proc/bus/pci
   pcilib: Cannot find any working access method.
   root@beaglebone:~#

Off I went and found a solution[1] which states that I should force the PCI_* defines to off *after* the configuration stage. So I go into my work directory and alter includes/net-snmp/net-snmp-config.h:

   /* define if you have pci_lookup_name() */
   #undef HAVE_PCI_LOOKUP_NAME

   /* Define to 1 if you have the <pci/pci.h> header file. */
   #undef HAVE_PCI_PCI_H

Then compile with:

bitbake net-snmp -c compile -f

Then

bitbake core-image-minimal

Quoted 9 lines

Which does net-snmp do_install and then builds the rootfs. However this makes no difference and it still fails with the same error message on start. Is my work flow for this wrong, or is it re-configuring, I'm at a bit of a loss of what to do now?

I suppose the correct procedure would be to find out why pcilibs is being detected and configured, then fix that. Could anyone point me in the right direction?

Regards,
Jack.

[1] http://stackoverflow.com/questions/9470494/snmpd-cannot-open-proc-bus-pci

It seems that udev is forcing PCI down every ones throats, is this necessary, can it be built without? There seems to be a lot of extra configuration in there to make it happen...

Onward ho!

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  http://www.embed.me.uk

--
#2 lore raw
Quoted 31 lines · Jack Mitchell
Quoted 30 lines · Jack Mitchell

Ok, so I managed to get net-snmp compiling however I now have an issue where the configure stage is picking up libpci and using that to configure net-snmp to look for pci devices on startup which my beaglebone doesn't have

   root@beaglebone:~# snmpd
   pcilib: Cannot open /proc/bus/pci
   pcilib: Cannot find any working access method.
   root@beaglebone:~#

Off I went and found a solution[1] which states that I should force the PCI_* defines to off *after* the configuration stage. So I go into my work directory and alter includes/net-snmp/net-snmp-config.h:

   /* define if you have pci_lookup_name() */
   #undef HAVE_PCI_LOOKUP_NAME

   /* Define to 1 if you have the <pci/pci.h> header file. */
   #undef HAVE_PCI_PCI_H

Then compile with:

bitbake net-snmp -c compile -f

Then

bitbake core-image-minimal

Which does net-snmp do_install and then builds the rootfs. However this makes no difference and it still fails with the same error message on start. Is my work flow for this wrong, or is it re-configuring, I'm at a bit of a loss of what to do now?

I suppose the correct procedure would be to find out why pcilibs is being detected and configured, then fix that. Could anyone point me in the right direction?

Regards,
Jack.

Quoted 8 lines
Quoted 3 lines

[1] http://stackoverflow.com/questions/9470494/snmpd-cannot-open-proc-bus-pci

It seems that udev is forcing PCI down every ones throats, is this necessary, can it be built without? There seems to be a lot of extra configuration in there to make it happen...

Onward ho!

As a stop gap till I manage to get to the bottom of this properly, doing:

bitbake core-image-minimal

to get the initial image and everything built properly

bitbake -c cleansstate pciutils

To remove pci.h from the sysroot

bitbake -c cleansstate net-snmp

to remove the net-snmp with pci config enabled

bitbake net-snmp

to rebuild net-snmp without pci config enabled (due to it not finding pci.h)

bitbake core-image-minimal

pciutils gets rebuilt, net-snmp stays configured without pci and everybody is happy (apart from the deterministic build goddess).

Regards,

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  http://www.embed.me.uk

--