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: bootstrap/3410: Cannot build gcc 3.0 for m68k-elf target; stage 2 compiler bug Date: Mon, 20 Aug 2001 09:16:00 -0000 [thread overview] Message-ID: <20010820161601.21417.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR bootstrap/3410; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/3410: Cannot build gcc 3.0 for m68k-elf target; stage 2 compiler bug Date: Mon, 20 Aug 2001 12:05:43 -0400 ----- Forwarded message from Faisal Akber <fakber@lineo.ca> ----- Delivered-To: rodrigc@gcc.gnu.org Date: Mon, 20 Aug 2001 11:59:19 -0400 (EDT) From: Faisal Akber <fakber@lineo.ca> To: rodrigc@gcc.gnu.org cc: fakber@lineo.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: bootstrap/3410: Cannot build gcc 3.0 for m68k-elf target; stage 2 compiler bug In-Reply-To: < 20010818153451.7315.qmail@sourceware.cygnus.com > Hi, I have just tried gcc-3.0.1 and built it for m68k-elf. It built cleanly. Thanks, -- Faisal Akber -- Lineo Canada Corp. -- fakber@lineo.ca On 18 Aug 2001 rodrigc@gcc.gnu.org wrote: > Synopsis: Cannot build gcc 3.0 for m68k-elf target; stage 2 compiler bug > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sat Aug 18 08:34:51 2001 > State-Changed-Why: > Does this problem still occur with gcc 3.0.1? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3410&database=gcc > ----- End forwarded message -----
next reply other threads:[~2001-08-20 9:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-20 9:16 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-16 5:16 rodrigc 2001-11-15 20:16 rodrigc 2001-08-18 8:34 rodrigc
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=20010820161601.21417.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).