public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@attbi.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6 Date: Thu, 21 Mar 2002 15:46:00 -0000 [thread overview] Message-ID: <20020321234604.31413.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/5167; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@attbi.com> To: Steven Sabean <Steven.Sabean@sun.com> Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6 Date: Thu, 21 Mar 2002 18:43:58 -0500 On Thu, Mar 21, 2002 at 03:21:26PM -0700, Steven Sabean wrote: > Seems like a good way to keep the number of open bugs to a minimum is to close > them without investigating at all, right? I don't care for your tone. Unlike you, I don't get paid by Sun to do this work, and am strictly a volunteer for the GCC project. So try to be nice. > Why don't you try following the link to the "successful build report" you > mention? > > You might notice that there is no report of a successful build of gcc-3.0.2 on > Solaris 2.6. There is a successful build report of gcc 3.0.4 on Solaris 2.6. gcc 3.0.4 has bugfixes on top of gcc 3.0.2. So, this bug report is not worth keeping open in my opinion. -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com
next reply other threads:[~2002-03-21 23:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-21 15:46 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-21 16:06 Steven Sabean 2002-03-21 14:26 Steven Sabean 2002-03-03 10:49 rodrigc 2002-01-07 12:46 Steven Sabean 2002-01-01 15:56 rodrigc 2001-12-20 11:46 steven.sabean
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=20020321234604.31413.qmail@sources.redhat.com \ --to=rodrigc@attbi.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).