This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: should UINT32 be a macro or typedef?
- From: Tom Tromey <tromey at redhat dot com>
- To: Adam Megacz <gcj at lists dot megacz dot com>
- Cc: java at gcc dot gnu dot org
- Date: 10 Dec 2001 13:24:13 -0700
- Subject: Re: should UINT32 be a macro or typedef?
- References: <86u1uyvoec.fsf@megacz.com>
- Reply-to: tromey at redhat dot com
>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:
Adam> Somewhere in the headers pulled in by libjava/boehm.cc, one
Adam> header wants UINT32 to be a #define, and another wants it to be
Adam> a typedef. I haven't figured out exactly where the conflict is,
Adam> but when I find it, which one is "right"?
Adam> Right now I just hacked it by #undef UINT32 in boehm.cc, but I'd
Adam> like to come up with a cleaner solution before I submit my
Adam> patch.
Do either the GC or libjava use this? I don't remember ever seeing
it. If that's the case then it is some kind of clash between system
headers. In that scenario any documented fix is fine.
Tom