There is no logic to add this -fsigned-char during configure. You
must have had it defined in an environment variable somewhere. I
guess I've never noticed this. Are there other platforms that you
know of that do this? Is this something we should definitely be
adding a configure check for?
David
Building many packages on LinuxPPC requires -fsigned-char in the gcc
options, to make the behavior consistent with Linux-x86. The ANSI
standard does not specify either way the default behavior, and for
some inscrutable reason, the PPC gcc chose the opposite convention
as x86. I think programs are supposed to specify signed or unsigned
if they really care, but most code assumes signed is the default.
The configure system for dx did this (automatically inserted
-fsigned-char) correctly on my LinuxPPC system, though. Is there
some stuff in dx being built without this string?
Marcus Mendenhall
Cleaning a few things up lately, I just found out that on my
LinuxPPC installation, char and signed char are different i.e. char
is unsigned char. Is this the same case for Linux Intel? Could
someone run the test:
#include <stdio.h>
int main() {
char a = -3;
if(a > 0)
printf("Ooops!\n");
return 0;
}
And let me know? If I change the char to signed char above then it
works as expected.
David
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
