public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/5944: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap failure)
Date: Wed, 13 Mar 2002 13:26:00 -0000 [thread overview]
Message-ID: <20020313212601.31383.qmail@sources.redhat.com> (raw)
The following reply was made to PR libgcj/5944; it has been noted by GNATS.
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: libgcj/5944: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap failure)
Date: Wed, 13 Mar 2002 22:20:26 +0100 (MET)
> >Category: libgcj
> >Responsible: unassigned
> >Synopsis: Use of uint32_t breaks libgcj bootstrap on Solaris 2.5.1
> >Arrival-Date: Wed Mar 13 12:16:05 PST 2002
Trying to bootstrap on Tru64 UNIX V4.0F, I noticed a similar problem: this
system doesn't have any definition of uint<n>_t in system headers, so
bootstrap with --enable-libgcj is broken on this platform as well.
Rainer
next reply other threads:[~2002-03-13 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 13:26 Rainer Orth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 12:16 Rainer Orth
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=20020313212601.31383.qmail@sources.redhat.com \
--to=ro@techfak.uni-bielefeld.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).