public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
h.b.furuseth@usit.uio.no, nobody@gcc.gnu.org
Subject: Re: other/3415: noisy build process with incomplete cleanup
Date: Sat, 21 Dec 2002 09:14:00 -0000 [thread overview]
Message-ID: <20021221171444.11937.qmail@sources.redhat.com> (raw)
Synopsis: noisy build process with incomplete cleanup
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Sat Dec 21 09:14:44 2002
State-Changed-Why:
I don't have such a machine, so would like to ask you whether
you can retry your experiment with gcc3.2.1, and see whether
the two files are still not deleted?
The thing with the warnings is intentional. The number
of warnings in the source code has also been greatly
reduced recently.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3415
next reply other threads:[~2002-12-21 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 9:14 bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 5:46 Hallvard B Furuseth
2001-06-25 14:26 Hallvard B Furuseth
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=20021221171444.11937.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=h.b.furuseth@usit.uio.no \
--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).