Re: signedness of char on ARM vs x86

On Sat, 5 Apr 2008, Juha Kuikka wrote:

> Char is indeed unsigned on ARM by default.
>
> http://www.arm.linux.org.uk/docs/faqs/signedchar.php
>
> You could try to give "-fsigned-char" to gcc when you build your library.
>
> - Juha

Yes, thank you. That clears up the few failures in "make check" and the
application works properly, too.

For opencv I did
"export CFLAGS=-fsigned-char; export PYTHON=/usr/bin/python2.5; ./configure ;
make ; make check"

cc. to maemo-users in case others run into this porting packages from
x86


> On Sat, Apr 5, 2008 at 9:40 PM, Andrew Daviel <advax@triumf.ca> wrote:

>> .... I find some compiler warnings such as
>> warning: comparison is always false due to limited range of data type
>> warning: converting of negative value `-0x00000000000000001' to `char'

....
>> By which I presume that "char" is signed on the 386 and unsigned on the
>> ARM.

--
Andrew