Iperf: can't compile on my arm-based Linux NAS device

Created on 28 Feb 2014  ·  7Comments  ·  Source: esnet/iperf

_From kaefert on July 16, 2013 23:59:05_

I wanted to try out iperf3.

On my Ubuntu machine I had no problem compiling and running it. However I usally use my NAS as server for my performance messurements, so I tried to get it compiled there also.

A few of my problems I could solve by installing
ipkg install gcc grep diffutils

but now I've got a problem with awk.
By default I've only got this:
[~/iperf-3.0b5] # awk
BusyBox v1.01 (2013.02.28-18:30+0000) multi-call binary

With that the configure script ended up with:
config.status: creating Makefile
awk: ./confeqzGIH/subs.awk:2: Unexpected token
config.status: error: could not create Makefile

Now I installed gawk 4.0.1-1, and now I get this:
config.status: creating Makefile
gawk: ./confjpxDtU/subs.awk:2: S["/; s/!.*/"]=LTLIBOBJS!%!_!# ""
gawk: ./confjpxDtU/subs.awk:2: ^ syntax error
(and a lot more of those)
config.status: error: could not create Makefile

Now is awk my problem, is there some other version thats needed, or is it something that happened previously in the config-script?

Here's the full output of ./configure with awk and gawk: http://pastebin.com/ytsQqs3j

_Original issue: http://code.google.com/p/iperf/issues/detail?id=78_

bug imported

Most helpful comment

_From bentolor on September 11, 2013 14:42:55_

For the records: The sed implementation is the issue.

I could workaround this using:

ipkg install sed -force-reinstall
export PATH=/opt/bin:$PATH

All 7 comments

_From [email protected] on July 23, 2013 11:03:24_

Owner: jdugan.esnet
Labels: Milestone-3.0-Release

_From kaefert on July 23, 2013 13:18:12_

I just checked, my Ubuntu machine also prints
awk --version
GNU Awk 4.0.1

So it must be something else than gawk that is causing those troubles.

_From jef.poskanzer on August 16, 2013 13:26:13_

Just sucessfully configured & compiled on an ARM-based Raspberry Pi, so this doesn't look like an ARM (byte order) issue.

_From bentolor on September 11, 2013 14:42:55_

For the records: The sed implementation is the issue.

I could workaround this using:

ipkg install sed -force-reinstall
export PATH=/opt/bin:$PATH

_From kaefert on September 13, 2013 01:45:22_

Thanks for the hint with sed! Now I can compile it, but when I try to run in server mode (didn't try client yet) it only prints me usage information like I called it wrong..?

[~/iperf-3.0b5/src] # ./iperf3 --version
Linux BLECHNAS 2.6.33.2 #1 Fri Apr 26 07:56:15 CST 2013 armv5tel unknown
iperf version 3.0-BETA5 (28 March 2013)

[~/iperf-3.0b5/src] # ./iperf3 --server
Usage: iperf [-s|-c host] [options]
...

_From jef.poskanzer on November 05, 2013 09:25:13_

This is almost certainly the signed/unsigned char issue with getopt. We fixed it in May, so the 28 March version would not have had the fix. Retry with a current version?

_From [email protected] on November 09, 2013 10:56:13_

closing, since should be fixed, and we dont have a way to test.

Status: Done

Was this page helpful?
0 / 5 - 0 ratings

Related issues

smcifrankp picture smcifrankp  ·  4Comments

Surendraknatarajan picture Surendraknatarajan  ·  9Comments

bbordereau picture bbordereau  ·  10Comments

danielaCasasv picture danielaCasasv  ·  4Comments

fefone picture fefone  ·  5Comments