public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
Date: Wed, 27 Nov 2002 13:56:00 -0000 [thread overview]
Message-ID: <20021120021604.26877.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/3758; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: David Abrahams <dave@boost-consulting.com>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: bootstrap/3758: GCC-3.0 doesn't build under cygwin / Bad diagnostic
reporting
Date: Tue, 19 Nov 2002 20:15:19 -0600 (CST)
> > Synopsis: GCC-3.0 doesn't build under cygwin / Bad diagnostic reporting
> >
> > State-Changed-From-To: open->feedback
> > State-Changed-Why:
> > This is a rather old bootstrap failure report, and gcc3.0
> > is no longer supported.
>
> Don't look at me! I reported this Sat Jul 21 10:46:00 PDT 2001!
Don't look at me neither, I am just checking old old reports of which I
think 90% can be closed since they no longer apply. I am just pinging
people to see what the present state is :-)
> > Can you please check whether you can build a newer version of
> > gcc on your platform and let us know about your findings?
>
> Of course I have built many more recent GCCs on my platform since
> then. Who could wait 18 months just to get going with GCC 3.x?
Thanks for your quick reply!
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-20 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 13:56 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 12:26 David Abrahams
2002-11-27 9:46 bangerth
2002-11-27 8:54 bangerth
2001-07-21 10:46 david.abrahams
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=20021120021604.26877.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--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).