Hi,
Just wanted to let you know that I could get version 5.2.3 to work with the
configuration and setup (small agent on embedded MIPS system) I described in my
problem. The lower versions might have worked but somehow I could not compile
them without PERL. The higher versions, 5.4 and 5.4.1 rc definitely didn't work
for me in this configuration.
I finally did need to include --with-mib-modules="ucd-snmp/dlmod" to get it to
work.
I will post more details as and when I discover them, and I'd post the details
of workaround for versions 5.4 or higher if I can create one.
Thanks for all your help.
-Kapil
----- Original Message ----
From: Kapil Sharma <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, July 26, 2007 12:05:40 PM
Subject: Re: Running Net-SNMP on embedded MIPS platform
Thomas Anders suggested that I could explicitly try to include ucd-snmp/dlmod
in the mib modules in configure, and see if it helps.
However, while
./configure --host=x86-linux --target=mips-linux --with-cc=mips-linux-gcc
--with-ar=mips-linux-ar --with-endianness=big --disable-debugging
--enable-mini-agent --without-kmem-usage --disable-manuals --with-cflags=-Os
--without-openssl --with-out-transports=TCP --disable-embedded-perl
--disable-perl-cc-checks --without-perl-modules --with-default-snmp-version="2"
--with-sys-contact="[EMAIL PROTECTED]" --with-sys-location="chandler"
--with-logfile="/var/log/snmpd.log" --with-persistent-directory="/var/net-snmp"
make
works fine,
./configure --host=x86-linux --target=mips-linux --with-cc=mips-linux-gcc
--with-ar=mips-linux-ar --with-endianness=big --disable-debugging
--enable-mini-agent --without-kmem-usage --disable-manuals --with-cflags=-Os
--without-openssl
--with-out-transports=TCP --disable-embedded-perl --disable-perl-cc-checks
--without-perl-modules --with-default-snmp-version="2"
--with-sys-contact="[EMAIL PROTECTED]" --with-sys-location="chandler"
--with-logfile="/var/log/snmpd.log" --with-persistent-directory="/var/net-snmp"
--with-mib-modules="ucd-snmp/dlmod"
make
does not, and gives this error:
/bin/sh ../libtool --mode=link mips-linux-gcc -Os -Ulinux -Dlinux=linux
-rpath /usr/local/lib -version-info 15:0:0 -o libnetsnmpmibs.la
mibgroup/ucd-snmp/dlmod.lo mibgroup/mibII/snmp_mib.lo
mibgroup/mibII/system_mib.lo mibgroup/mibII/sysORTable.lo
mibgroup/mibII/vacm_vars.lo mibgroup/snmpv3/snmpEngine.lo
mibgroup/snmpv3/snmpMPDStats.lo mibgroup/snmpv3/usmStats.lo
mibgroup/snmpv3/usmUser.lo mibgroup/util_funcs.lo
mibgroup/mibII/vacm_context.lo mib_modules.lo auto_nlist.lo
mips-linux-gcc -shared mibgroup/ucd-snmp/.libs/dlmod.o
mibgroup/mibII/.libs/snmp_mib.o
mibgroup/mibII/.libs/system_mib.o mibgroup/mibII/.libs/sysORTable.o
mibgroup/mibII/.libs/vacm_vars.o mibgroup/snmpv3/.libs/snmpEngine.o
mibgroup/snmpv3/.libs/snmpMPDStats.o mibgroup/snmpv3/.libs/usmStats.o
mibgroup/snmpv3/.libs/usmUser.o mibgroup/.libs/util_funcs.o
mibgroup/mibII/.libs/vacm_context.o .libs/mib_modules.o .libs/auto_nlist.o
-Wl,-soname -Wl,libnetsnmpmibs.so.15 -o .libs/libnetsnmpmibs.so.15.0.0
mips-linux-gcc: mibgroup/ucd-snmp/.libs/dlmod.o: No such file or directory
make[1]: *** [libnetsnmpmibs.la] Error 1
make[1]: Leaving directory `/home/kasharma/Jaloro/projects/net-snmp-5.4/agent'
make: *** [subdirs] Error 1
The dlmod.o does not exist. I would think a dependency would have been compiled
before it was used. The Makefile in agent/mibgroup lists dlmod.o correctly:
mib_module_list_o= \
ucd-snmp/dlmod.o
\
mibII/snmp_mib.o \
mibII/system_mib.o \
mibII/sysORTable.o \
mibII/vacm_vars.o \
snmpv3/snmpEngine.o \
snmpv3/snmpMPDStats.o \
snmpv3/usmStats.o \
snmpv3/usmUser.o \
util_funcs.o \
mibII/vacm_context.o \
And all other .o are getting created, but for dlmod, only dlmo.lo is created,
not dlmod.o.
Any ideas are much appreciated.
Thanks,
Kapil
Dave Shield <[EMAIL PROTECTED]> wrote: On 26/07/07, Need Help wrote:
> I thought you always had to do a "make install" to generate the true snmpd
> master agent executable, otherwise I thought the "snmpd" was just a script.
Kapil is installing a subtly different file, which is the actual binary.
> I always perform a "make install" and then copy stuff over to the target
> machine and use it.
That is a much safer approach in general.
If you've got something that works, then stick to it.
Don't worry about how other people might be doing things.
Concentrate on your own problems.
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now
>> http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Got a little couch potato?
Check out fun summer activities for kids.
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
