From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-11124-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 29676 invoked by alias); 1 Jan 2003 19:12:10 -0000
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
Received: (qmail 29668 invoked from network); 1 Jan 2003 19:12:08 -0000
Received: from unknown (HELO lifesupport.shutdown.com) (66.93.79.177)
  by 209.249.29.67 with SMTP; 1 Jan 2003 19:12:08 -0000
Received: (from llewelly@localhost)
	by lifesupport.shutdown.com (8.11.2/8.11.2) id h01J9O521908;
	Wed, 1 Jan 2003 11:09:24 -0800 (PST)
To: Oliver Kullmann <O.Kullmann@Swansea.ac.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error compiling GCC 3.2.1
Reply-To: gcc-help@gcc.gnu.org
References: <200212270550.18988.bane@uchicago.edu>
	<20021228162641.GB16019@swan.ac.uk>
From: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com>
Date: Wed, 01 Jan 2003 19:12:00 -0000
In-Reply-To: <20021228162641.GB16019@swan.ac.uk>
Message-ID: <x31y3wk7q5.fsf@lifesupport.shutdown.com>
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2003-01/txt/msg00001.txt.bz2

Oliver Kullmann <O.Kullmann@Swansea.ac.uk> writes:

> Hi,
> 
> I have exactly the same problem (posted in also on this list,
> and sent an error report, but yet no answer).
[snip]

Unfortunately no one knows the answer. Here are some suggestions:

(a) Try getting a pre-built gcc 3.2.1 binary and building with that.

(b) Double check the versions of the tools you use to build
    gcc. 2.95.3 is probably solid, (I built 3.2.1 with 2.95.3 on
    FreeBSD, I know others have on other platforms.) so check your
    binutils versions first. If you have experimental/unofficial
    binutils, try replacing them. (Note: Some linux distros ship with
    experimental/unofficial binutils - so you may have them and not
    know it.)

(c) If you have a linux distro that builds everything with every
    optimization flag (e.g., mandrake, which uses -03 -fomit-frame-pointer
    -fexpensive-optimization -march=pentiumpro -mcpu=pentiumpro, and
    others I can't recall) try building gcc 2.95.3 without these
    optimizations, and use the new 2.95.3 for building 3.2.1 .

(d) Use 'make bootstrap4' instead of make bootstrap. This adds an
    additional stage; normally, the stage1 compiler builds the stage2
    compiler with the flags -g -O2. Using make bootstrap4, the stage1
    compiler builds the stage2 compiler with no optimization flags
    (reducing the chance that it will be miscompiled) and the stage2
    compiler builds the stage3 compiler with -g -O2.

(e) Try 'make BOOT_CFLAGS='-O' bootstrap ' or
    make BOOT_CFLAGS='-O0' bootstrap to build gcc with fewer
    optimizations.