public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7691: --enable-cxx-flags configure option broken
Date: Sat, 02 Nov 2002 15:06:00 -0000 [thread overview]
Message-ID: <20021102230601.18399.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/7691; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: bkoz@gcc.gnu.org, 7zbuodeyr001@sneakemail.com, gcc-bugs@gcc.gnu.org,
pme@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: libstdc++/7691: --enable-cxx-flags configure option broken
Date: Sat, 2 Nov 2002 18:01:11 -0500
On Sat, Nov 02, 2002 at 01:50:46AM -0000, bkoz@gcc.gnu.org wrote:
> Synopsis: --enable-cxx-flags configure option broken
>
> State-Changed-From-To: analyzed->feedback
> State-Changed-By: bkoz
> State-Changed-When: Fri Nov 1 17:50:45 2002
> State-Changed-Why:
> I think this has been fixed, correct?
None of the proposed patches have been applied to the top-level configury.
The continued cleanups may have fixed it as an accidental side-effect, but I
haven't tested it. I made a ping or two and nobody ever answered.
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-11-02 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 15:06 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 19:24 pme
2002-11-01 17:50 bkoz
2002-08-28 22:36 pme
2002-08-22 15:58 7zbuodeyr001
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=20021102230601.18399.qmail@sources.redhat.com \
--to=phil@jaj.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=pme@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).