sudonym1 / iperf

Automatically exported from code.google.com/p/iperf
Other
0 stars 0 forks source link

Error compiling iperf3 on Centos 5.4 #141

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. ./configure
2. make

What is the expected output? What do you see instead?

compiling without errors.

Instead:

Making all in src
make[1]: Entering directory `/root/iperf-3.0.1/src'
make  all-am
make[2]: Entering directory `/root/iperf-3.0.1/src'
gcc -DHAVE_CONFIG_H -I.     -g -O2 -MT iperf_tcp.o -MD -MP -MF 
.deps/iperf_tcp.Tpo -c -o iperf_tcp.o iperf_tcp.c
iperf_tcp.c: In function 'iperf_tcp_listen':
iperf_tcp.c:189: error: 'TCP_CONGESTION' undeclared (first use in this function)
iperf_tcp.c:189: error: (Each undeclared identifier is reported only once
iperf_tcp.c:189: error: for each function it appears in.)
iperf_tcp.c: In function 'iperf_tcp_connect':
iperf_tcp.c:378: error: 'TCP_CONGESTION' undeclared (first use in this function)
make[2]: *** [iperf_tcp.o] Error 1
make[2]: Leaving directory `/root/iperf-3.0.1/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/iperf-3.0.1/src'
make: *** [all-recursive] Error 1

What version of the product are you using? On what operating system?

iperf 3.0.1 on Centos 5.4 (x86-64)

Please provide any additional information below.

Original issue reported on code.google.com by bruno.fo...@gmail.com on 20 Feb 2014 at 12:22

GoogleCodeExporter commented 9 years ago
This problem has already been fixed on trunk in revision 2609f9167672 (no issue 
was filed for it).  I'm planning to make a bugfix release of iperf3 sometime in 
the next few weeks; it will have this code change in it.

I'm marking it fixed for 3.1 at the moment, but I'm going to have to do some 
munging around of milestone labels to reflect release engineering plans.

Original comment by bmah@es.net on 20 Feb 2014 at 12:31

GoogleCodeExporter commented 9 years ago
Great!
I will get the revision.

Thanks a lot.

Original comment by bruno.fo...@gmail.com on 20 Feb 2014 at 12:32

GoogleCodeExporter commented 9 years ago
I got the exact same error on SLES 10 SP4.

Original comment by keith.la...@gmail.com on 26 Feb 2014 at 3:06