You can't include them as a library since the base agent won't know what
init_ functions to call to start you code.
Instead, put your code in the agent/mibgroup directory and use
--with-mib-modules="file1 file2" etc to get them to compile in and the
init_ routines to be found and used.
> On Thu, 15 Apr 2010 14:08:09 +0900 (KST), "»ý°¢Çϱâ"
> said:
b> I make shared library and static library using my source library files.
b> and linked them
b> but useless...
b> It is my install script file
You can't include them as a library since the base agent won't know what
init
I 'm trying to cross-compile net-snmp-5.3.2 with my mib-module and my personal library, not form of agentx
but I failed every time.
I think that it is a problem of configuration option.
I make shared library and static library using my source library files.
and linked them
Jordan,
The openSSL library is only required for encryption, if you do not need
net-snmp to support encryption you can drop the openssl and encryption
references from the configure line.
If you do require full V3 encryption support, the method for installing
the openssl development files will
Jordan,
You need to use the makefile properly configured for the target.
This script builds the 5.4.1agent only for an arm target, tweak to suit
your requirements and version.
cd net-snmp-5.4.1/
#1 single find command and xargs chokes due to bash line limitation, process
sequentially
find -nam
If I was going to use a cross compiler on net-snmp, how would I do this?
I used a gcc compiler for an Arm processor on smpd.c, but it returned a
bunch of errors because it couldn't find the includes.
Thanks,
Jordan
--
Th
Dear Wolfgang, The code i compiled worked fine. Following your instruccions i have been able to create the rpm packages. So everything is perfect. Thanks for your kindly help and thanks for your valuable information.
¡ Happy New Year ! Héctor OrónOn 12/27/05, Wolfgang Denk <[EMAIL PROTECTED]> wro
-> ${CROSS_COMPILE}rpmbuild -ba net-snmp.spec
[...]
checking for correct flags to ps...
configure: error: Endianness has been specified, but you are not cross-compiling.
error: Bad exit status from /home/otros/hecormar/eldk/var/tmp/rpm-tmp.50809 (%build)
RPM build errors:
Bad exit status from
In message <[EMAIL PROTECTED]> you wrote:
>
> I have tried ELDK net-snmp binaries, i have added all missing shared libs,
> and i get:
>
> / # snmpd -H
> snmpd: error in loading shared libraries
> /lib/libm.so.6: undefined symbol: __sim_disabled_exceptions
>
> BTW, snmpd ask for libcrypto.so.0.9.8
libcrypto.so.0.9.7a, i have done a symlink as a workarround.
Should i just try to build ELDK for my target ?
Best Regards,
Hector OronOn 12/9/05, Wolfgang Denk <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]> you wrote:>> I've been trying to cross-compile net-snmp for ppc
In message <[EMAIL PROTECTED]> you wrote:
>
> I've been trying to cross-compile net-snmp for ppc over i386. I have build
> a script with some of the options that we should select. I'm able to
> generate my binary file, but when i start snmpd agent it doesn't
Hello folks,
I've been trying to cross-compile net-snmp for ppc over i386. I have
build a script with some of the options that we should select. I'm able
to generate my binary file, but when i start snmpd agent it doesn't
work as I expect.
Target: MPC-855 (ppc), glibc-1.99
12 matches
Mail list logo
