This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: javaop.h type collision on AIX
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: javaop.h type collision on AIX
- From: Per Bothner <bothner at cygnus dot com>
- Date: Sat, 14 Nov 1998 15:33:39 -0800
- cc: egcs-bugs at cygnus dot com
> I think that there are a couple of problems: signed-ness
> assumptions and not protecting all types of previous definitions.
It seems like there is a third problem: Why are we seeing the
conflicting definition anyway? Is AIX polluting the application
namespace, or is there something else going on?
The signed-ness problem is complicated because "signed char"
is not valid in K&R C. We probably don't care (the Java
compiler should only be compiled using gcc), but for robustness
the following may make sense:
- Remove the definition of int8.
- Replace the definition of jbyte by:
#ifdef __STDC__
typedef signed char jbyte;
#else
typedef char jbyte;
#endif
--Per Bothner
Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner