public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Boyd Lynn Gerber <gerberb@zenez.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10517: Make bootstrap fails to compile with abs' is already declared in this scope in complex_io.lo Date: Mon, 19 May 2003 05:16:00 -0000 [thread overview] Message-ID: <20030519051600.12726.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10517; it has been noted by GNATS. From: Boyd Lynn Gerber <gerberb@zenez.com> To: giovannibajo@libero.it, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: bootstrap/10517: Make bootstrap fails to compile with abs' is already declared in this scope in complex_io.lo Date: Sun, 18 May 2003 23:14:43 -0600 (MDT) On 17 May 2003 giovannibajo@libero.it wrote: > Synopsis: Make bootstrap fails to compile with abs' is already declared in this scope in complex_io.lo > State-Changed-From-To: open->feedback > State-Changed-By: bajo > State-Changed-When: Sat May 17 06:56:38 2003 > State-Changed-Why: > See Dara's question. If the bug is still present in GCC 3.3, > would you please attach a preprocessed output of the failing > file, as described in http://gcc.gnu.org/bugs.html? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10517 I did not see the problem with gcc-3.3 Thanks, -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
next reply other threads:[~2003-05-19 5:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 5:16 Boyd Lynn Gerber [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 8:50 giovannibajo 2003-05-17 6:56 giovannibajo 2003-05-17 2:26 Dara Hazeghi 2003-05-17 1:06 Dara Hazeghi 2003-05-14 18:16 Dara Hazeghi 2003-04-28 5:36 gerberb
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=20030519051600.12726.qmail@sources.redhat.com \ --to=gerberb@zenez.com \ --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).