public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/3355: [alphaev6-dec-osf5.0] Build of gcc3.0 fails Date: Wed, 21 May 2003 08:29:00 -0000 [thread overview] Message-ID: <20030521082602.13056.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3355; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: P.Jackway@cssip.uq.edu.au, gcc-gnats@gcc.gnu.org, rodrigc@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/3355: [alphaev6-dec-osf5.0] Build of gcc3.0 fails Date: Wed, 21 May 2003 01:15:01 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=3355 Hello, there have been a good number of reports of osf build failures :-( However, Roger Sayle has been doing a fair bit of work on the issue, and there have been some reports of success. Would it be possible for you to check whether this problem still exists in 3.3 or current 3.3 cvs branch? Thanks, Dara
next reply other threads:[~2003-05-21 8:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-21 8:29 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 9:06 Dara Hazeghi 2002-12-05 13:30 bangerth 2002-11-27 7:58 bangerth
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=20030521082602.13056.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.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).