From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14923 invoked by alias); 20 May 2003 16:27:11 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 14903 invoked from network); 20 May 2003 16:27:10 -0000 Received: from unknown (HELO e3.ny.us.ibm.com) (32.97.182.103) by sources.redhat.com with SMTP; 20 May 2003 16:27:10 -0000 Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206]) by e3.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h4KGQZE2200250; Tue, 20 May 2003 12:26:35 -0400 Received: from unknown.host (d01av02.pok.ibm.com [9.56.224.216]) by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4KGQWB4114836; Tue, 20 May 2003 12:26:33 -0400 Received: (from janis@localhost) by unknown.host (8.9.3/8.9.3) id JAA01397; Tue, 20 May 2003 09:25:36 -0700 Date: Tue, 20 May 2003 16:27:00 -0000 From: Janis Johnson To: John Sincock Cc: Janis Johnson , gcc-help@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: extremely disappointing bootstrap problems building gcc on linux :( (probably solved) Message-ID: <20030520092536.A1377@us.ibm.com> References: <200305171200.h4HC0acA251822@e35.co.us.ibm.com> <20030519123533.A3323@us.ibm.com> <200305201240.h4KCeR82101192@e6.ny.us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200305201240.h4KCeR82101192@e6.ny.us.ibm.com>; from jss@au.mensa.org on Tue, May 20, 2003 at 10:10:14PM +0930 X-SW-Source: 2003-05/txt/msg00163.txt.bz2 On Tue, May 20, 2003 at 10:10:14PM +0930, John Sincock wrote: > I will probably do that this weekend and send in a quick report to this > list if it is succesful... To include your successful build in the GCC 3.3 build status list at http://gcc.gnu.org/gcc-3.3/buildstat.html, please follow the instructions at the end of the installation instructions; that way your information will be available to other people building on the same or a similar platform. In addition to the recommended information about your build you can include any additional information that might be helpful, including problems you encountered and how you got around them. Janis