net-snmp-coders

Re: compiling issues with libsnmp.a

[<ni...@ba...>]

On Fri, 24 Nov 2000 12:58:56 -0500 (EST) Jas...@ms... wrote:
>	hey all -- got the daemons set up and running doing everything i
>want...now i'm trying to extend the daemon following the exmample on the
>webpage: 
>http://net-snmp.sourceforge.net/tutorial/toolkit/demoapp/snmpdemoapp.c
>
>when I compiled my own test code, i made sure to add the appropriate
>directory to my -L path as well as teh right ones to my -I path and also
>added -lsnmp -- still getting the following:
>
>g++ -L/ms/user/j/jasong/proj/dev/lib -lthread -lposix4 -lsocket -lnsl
>-lsnmp thr
>ead.o semaphore.o mutex.o snmpapi.o ebdlistener.o main.C -o emsagent
>Undefined                       first referenced
> symbol                             in file
>init_snmp                           snmpapi.o

The linker processes files in the order on the command line, and it processes a
library when it meets it. You should always put libraries after any .o files
that uses them.

/Niels

-- 
Get your firstname@lastname email for FREE at http://Nameplanet.com/?su

Re: compiling issues with libsnmp.a

[<ni...@ba...>]

On Fri, 24 Nov 2000 16:15:32 -0500 (EST) Jas...@ms... wrote:
>	thanks for the tip, neils -- that seems to hold true for any
>user-defined libraries, but if you choose to do:
>	g++ -lsocket -lnsl <etc...> main.C foo.o bar.o -o baz
>
>this DOES work...whereas...
>	g++ -L. -lsnmp -nmylib main.C foo.o bar.o -o baz
>
>does NOT...is there a deeper explanation to this?

I don't know. Maybe g++ in its infinite wisdom always add -lsocket -lnsl -l to
the end of the load ?

/Niels

-- 
Get your firstname@lastname email for FREE at http://Nameplanet.com/?su

Re: compiling issues with libsnmp.a

[<Jas...@ms...>]

	sadly, i tried this with 3 compilers (gcc/g++, Lexa, and SunPro),
and they all produce the same odd behavior.

Re: compiling issues with libsnmp.a

[<ni...@ba...>]

On Fri, 24 Nov 2000 18:56:14 -0500 (EST) Jas...@ms... wrote:
>	sadly, i tried this with 3 compilers (gcc/g++, Lexa, and SunPro),
>and they all produce the same odd behavior.

Just keep your libraries last, in dependency order, it always works.

/Niels

-- 
Get your firstname@lastname email for FREE at http://Nameplanet.com/?su

Re: compiling issues with libsnmp.a

[<Jas...@ms...>]

	thanks for the tip, neils -- that seems to hold true for any
user-defined libraries, but if you choose to do:
	g++ -lsocket -lnsl <etc...> main.C foo.o bar.o -o baz

this DOES work...whereas...
	g++ -L. -lsnmp -nmylib main.C foo.o bar.o -o baz

does NOT...is there a deeper explanation to this?

cheers,

jason