public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Adam Megacz <adam@megacz.com>
Cc: gcc-gnats@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap failure)
Date: Wed, 13 Mar 2002 14:40:00 -0000	[thread overview]
Message-ID: <15503.54620.761421.899604@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <86henk3xp5.fsf@megacz.com>

Adam Megacz writes:

> Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> writes:
> > 2002-02-06  Adam Megacz <adam@xwt.org>
> > 
> >         * gnu/gcj/io/shs.h, gnu/gcj/io/shs.cc, gnu/gcj/io/natSimpleSHSStream.cc:
> >         use uint<n>_t instead of LONG and BYTE
> > 
> > which unconditionally uses uint<n>_t
> 
> Nope, check shs.h (included from shs.cc):
> 
>   #include<config.h>
>   #if HAVE_INTTYPES_H
>   # include <inttypes.h>
>   #else
>   # if HAVE_STDINT_H
>   #  include <stdint.h>
>   # endif
>   #endif
> 
> If your system does not have one of these headers, it is not C99
> compliant. GCJ does not build on non-C99-compliant systems.

but this is both unlike the way libstdc++ handles this and a (completely
unnecessary) regression from GCC 3.0.x.

	Rainer

       reply	other threads:[~2002-03-13 22:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200203132014.VAA27030@tamarinde.TechFak.Uni-Bielefeld.DE>
     [not found] ` <86henk3xp5.fsf@megacz.com>
2002-03-13 14:40   ` Rainer Orth [this message]
2002-03-13 15:18     ` Adam Megacz
2002-03-13 15:40       ` Anthony Green
2002-03-14  2:56         ` Rainer Orth
2002-03-15 13:07           ` Tom Tromey
2002-03-15 13:33             ` Rainer Orth
2002-03-15 13:41               ` Tom Tromey
2002-03-15 14:45                 ` Rainer Orth
2002-04-02 18:49                   ` Tom Tromey
2002-03-15 13:43               ` Tom Tromey
2002-03-15 13:49                 ` Rainer Orth
2002-03-15 14:01                   ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15503.54620.761421.899604@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=adam@megacz.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).