[netperf-talk] Netperf 2.3.7 from OpenSS7

Rick Jones rick.jones2 at hp.com
Mon Oct 26 10:06:33 PDT 2009


I would like to keep the discussion in netperf-talk on the off-chance that 
someone else in the future might run into the same problem.

Frank Schuster wrote:
> Hello,
> 
> thank you for your reply.
> I try to install the netperf-2.4.5.tar.gz under debian 5.0.
> 
> If I use ./configure --enable-sctp it runs without errors but the lines where sctp comes in:
> checking for netinet/sctp.h... no
> checking for main in -lsctp... no
> checking for struct sctp_event_subscribe.sctp_adaptation_layer_event... no
> 
> There is standing always no in the lines with sctp. My question is therefore,
> what packet I need additional?

That is an exceedingly good question.   It may come-down to comparing the 
OpenSS7 modified older bits with the current netperf bits to see what they 
changed in detecting SCTP support.

None of my immediately available systems have SCTP on them for checking :(

> 
> 
> And the second question is, if I do make after configure (yes, I do it without sctp) I see this:
> /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/libsocket.a(libsocket_la-socket.o): In function `__sock_sendto_r':
> /usr/src/build_opennss7/strsock/../../openss7-0.9.2.G/strsock/src/lib/socket.c:1318: undefined reference to `__libc_sendto'
> /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/libsocket.a(libsocket_la-socket.o): In function `__sock_accept_r':
> /usr/src/build_opennss7/strsock/../../openss7-0.9.2.G/strsock/src/lib/socket.c:514: undefined reference to `__libc_accept'
> /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/libsocket.a(libsocket_la-socket.o): In function `__sock_bind_r':
> ...and so on.

That's something the openss7 support folks will have to weigh-in on.  It looks 
like they make some non-trivial changes to include files.

> I searched the web for this error and what I only found is that I need the libc. But I have installed the libc, I'm using currently the gcc in version 4.3.2.
> Do you know something what I can do there?
> Is this a problem with Debian 5.0 or someting else?



More information about the netperf-talk mailing list