public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pgonzalez at bluel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/8307] libstdc++ fails to compile because of fixincludes headers Date: Sun, 21 Sep 2003 15:00:00 -0000 [thread overview] Message-ID: <20030921103607.25985.qmail@sources.redhat.com> (raw) In-Reply-To: <20021021222600.8307.pgonzalez@bluel.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8307 ------- Additional Comments From pgonzalez at bluel dot com 2003-09-21 10:36 ------- Sorry I didn't respond sooner. I am happy with this outcome. I've been able to workaround the bugs by deleting the bad headers, and the problem seemed to have been fixed in a recent 3.4 snapshot.
next prev parent reply other threads:[~2003-09-21 10:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021021222600.8307.pgonzalez@bluel.com> 2003-08-05 1:53 ` neroden at gcc dot gnu dot org 2003-08-24 18:19 ` dhazeghi at yahoo dot com 2003-09-19 17:57 ` pinskia at gcc dot gnu dot org 2003-09-21 15:00 ` pgonzalez at bluel dot com [this message] [not found] <20021021222600.8307.gonz@ratloop.com> 2003-06-08 7:57 ` dhazeghi@yahoo.com 2003-06-17 16:10 ` gonz@ratloop.com 2003-07-20 21:42 ` dank at kegel dot com
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=20030921103607.25985.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).