From mboxrd@z Thu Jan  1 00:00:00 1970
From: Zack Weinberg <zack@codesourcery.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Top-level Makefile
Date: Fri, 30 Nov 2001 20:16:00 -0000
Message-ID: <20011130201643.A32361@codesourcery.com>
References: <10112010256.AA00279@vlsi1.ultra.nyu.edu>
X-SW-Source: 2001-11/msg01680.html
Message-ID: <20011130201600.2BwAJEt-b2TPfisJVz6XM9DZAj_jqScSmeUwpgK2baw@z>

On Fri, Nov 30, 2001 at 09:56:05PM -0500, Richard Kenner wrote:
>     Can you post the precise sequence of commands you are using, starting
>     from an empty build directory?
> 
> Well I'm *not* starting from an empty build directory.  I'm doing
> ./config.status or explicitly rerunning configure.

Ah.  Of course David's trick won't work in that case.

However, if you _do_ start from an empty directory, I will be very
surprised if it doesn't.

For reference, this is the script I have sitting at the top of all my
source trees:

#! /bin/sh

srcdir=`dirname $0`
prefix=$HOME/install/${srcdir##*/}
set -ex
#DWARF=--with-dwarf2
#CHECK=--enable-checking
#CHECK=--disable-checking
THREADS=--enable-threads=posix
#SHARED=--enable-shared
#GETTEXT=--with-included-gettext
$srcdir/configure --prefix=$prefix \
	$DWARF $CHECK $THREADS $SHARED $GETTEXT >Lc 2>&1
/usr/bin/time make bootstrap >Lb 2>&1
/usr/bin/time make -k check  >Lk 2>&1

and when I say I bootstrapped the compiler I mean I ran this script
starting from an empty build directory.  It is my understanding that
this is the preferred way to do things.

Try sticking 

CONFIG_SHELL=/path/to/bash
SHELL=/path/to/bash
export SHELL CONFIG_SHELL

at the top of that script, and running it from your build dir, like this:

$ ../src/gcc/build-it

zw