This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_tinstead of LONG and BYTE

From: Anthony Green <green at redhat dot com>
To: Adam Megacz <patches at lists dot megacz dot com>
Cc: java-patches at gcc dot gnu dot org
Date: 07 Feb 2002 07:13:16 -0800
Subject: Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_tinstead of LONG and BYTE
References: <86sn8lmwww.fsf@megacz.com> <86g04lmw9n.fsf@megacz.com><87d6zp9bvh.fsf@creche.redhat.com> <867kpwlrsi.fsf@megacz.com>

On Fri, 2002-02-01 at 15:13, Adam Megacz wrote:
> 
> Tom Tromey <tromey@redhat.com> writes:
> > Can we assume uint<n>_t on all platforms?  Or would we need configury
> > support here?
> 
> Isn't that stuff pretty standard?
> 
> It's available on all the platforms gcj supports (win32, linux,
> solaris, macosx).

No.  This change broke my xscale-elf build which uses the newlib C
library.

AG

References:
- WIN-09: shs.h undef LONG
  - From: Adam Megacz
- Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_t instead of LONG and BYTE
  - From: Adam Megacz
- Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_t instead of LONG and BYTE
  - From: Tom Tromey
- Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_t instead of LONG and BYTE
  - From: Adam Megacz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]