davie1008 / iperf

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

can't compile on my arm-based Linux NAS device #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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 reported on code.google.com by kaef...@gmail.com on 17 Jul 2013 at 6:59

GoogleCodeExporter commented 9 years ago

Original comment by bltier...@es.net on 23 Jul 2013 at 6:03

GoogleCodeExporter commented 9 years ago
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.

Original comment by kaef...@gmail.com on 23 Jul 2013 at 8:18

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

Original comment by jef.posk...@gmail.com on 16 Aug 2013 at 8:26

GoogleCodeExporter commented 9 years ago
For the records: The sed implementation is the issue.

I could workaround this using:

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

Original comment by bento...@gmail.com on 11 Sep 2013 at 9:42

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
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]
...

Original comment by kaef...@gmail.com on 13 Sep 2013 at 8:45

GoogleCodeExporter commented 9 years ago
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?

Original comment by jef.posk...@gmail.com on 5 Nov 2013 at 5:25

GoogleCodeExporter commented 9 years ago
closing, since should be fixed, and we dont have a way to test.

Original comment by bltier...@es.net on 9 Nov 2013 at 6:56