Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signedness issue on ARM platform #49

Closed
bmah888 opened this issue Feb 28, 2014 · 4 comments
Closed

signedness issue on ARM platform #49

bmah888 opened this issue Feb 28, 2014 · 4 comments

Comments

@bmah888
Copy link
Contributor

bmah888 commented Feb 28, 2014

From edvinas.stunzenas on September 05, 2012 08:11:18

By default ARM processors typically use unsigned char for char type. That why signed char use must be forced.
I used arm-linux-gcc-4.2.1 compiler.

Submitting patch for this problem to solve:

diff -r dafbddb0e039 src/Makefile.in
--- a/src/Makefile.in Mon Aug 20 14:35:58 2012 -0700
+++ b/src/Makefile.in Wed Sep 05 18:08:55 2012 +0300
@@ -266,7 +266,7 @@

Specify the sources and various flags for the iperf binary

iperf3_SOURCES = main.c
-iperf3_CFLAGS = -g -Wall
+iperf3_CFLAGS = -g -Wall -funsigned-char
iperf3_LDADD = libiperf.a
iperf3_LDFLAGS =

Tested with:
arm-linux-gcc-4.2.1
mipsel-linux-gcc-4.1.2

Original issue: http://code.google.com/p/iperf/issues/detail?id=49

@bmah888
Copy link
Contributor Author

bmah888 commented Feb 28, 2014

From bltierney@es.net on March 12, 2013 15:39:52

Owner: jdugan@es.net

@bmah888
Copy link
Contributor Author

bmah888 commented Feb 28, 2014

From bltierney@es.net on March 12, 2013 15:47:56

Labels: Milestone-3.0-Release

@bmah888
Copy link
Contributor Author

bmah888 commented Feb 28, 2014

From jef.poskanzer on May 06, 2013 09:45:09

Just fixed one case of signed/unsigned char problem, with getopt_long. Not enough info in this problem description to know if there are other instances.

@bmah888
Copy link
Contributor Author

bmah888 commented Feb 28, 2014

From jef.poskanzer on August 16, 2013 13:24:35

Found & fixed another signed/unsigned char problem. That's probably all.

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant