public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/3301: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build Date: Fri, 17 Aug 2001 14:26:00 -0000 [thread overview] Message-ID: <20010817212601.21516.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/3301; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/3301: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build Date: Fri, 17 Aug 2001 17:22:30 -0400 ----- Forwarded message from Daniel Elstner <daniel.elstner@gmx.net> ----- Delivered-To: rodrigc@gcc.gnu.org Subject: Re: c++/3301: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build From: Daniel Elstner <daniel.elstner@gmx.net> To: rodrigc@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org In-Reply-To: < 20010812200636.6253.qmail@sourceware.cygnus.com > X-Mailer: Evolution/0.12 (Preview Release) Date: 17 Aug 2001 22:34:42 +0200 Am 12 Aug 2001 20:06:36 +0000 schrieb rodrigc@gcc.gnu.org: > Synopsis: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sun Aug 12 13:06:36 2001 > State-Changed-Why: > I cannot reproduce your problem with > gcc 3.0.1 20010811. > > Can you download a newer gcc snapshot and try again? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3301&database=gcc I tried again with a current gcc-3.0.1 snapshot and one from cvs HEAD, too. Both work just fine now. Regards, --Daniel ----- End forwarded message -----
next reply other threads:[~2001-08-17 14:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-17 14:26 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-08-17 14:56 rodrigc 2001-08-12 13:06 rodrigc 2001-06-20 12:46 daniel.elstner
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=20010817212601.21516.qmail@sourceware.cygnus.com \ --to=rodrigc@mediaone.net \ --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: 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).