From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25038 invoked by alias); 21 Mar 2002 22:26:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 25009 invoked by uid 71); 21 Mar 2002 22:26:04 -0000 Date: Thu, 21 Mar 2002 14:26:00 -0000 Message-ID: <20020321222604.25008.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Steven Sabean Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6 Reply-To: Steven Sabean X-SW-Source: 2002-03/txt/msg00812.txt.bz2 List-Id: The following reply was made to PR bootstrap/5167; it has been noted by GNATS. From: Steven Sabean To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, steven.sabean@sun.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6 Date: Thu, 21 Mar 2002 15:21:26 -0700 (MST) Seems like a good way to keep the number of open bugs to a minimum is to close them without investigating at all, right? 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. That is because it has never happened. -Steve Sabean Sun Microsystems > To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org, steven.sabean@sun.com > Subject: Re: bootstrap/5167: gcc-3.0.2 fails to bootstrap on Solaris 2.6 > > Synopsis: gcc-3.0.2 fails to bootstrap on Solaris 2.6 > > State-Changed-From-To: feedback->closed > State-Changed-By: rodrigc > State-Changed-When: Sun Mar 3 10:49:17 2002 > State-Changed-Why: > Successful boostrap reports on this platform here: > http://gcc.gnu.org/gcc-3.0/buildstat.html > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=51 67