From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11580 invoked by alias); 17 May 2003 09:06:00 -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 11550 invoked by uid 71); 17 May 2003 09:06:00 -0000 Date: Sat, 17 May 2003 09:06:00 -0000 Message-ID: <20030517090600.11546.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Dara Hazeghi Subject: Re: bootstrap/10811: libjava/libltdl/configure fails Reply-To: Dara Hazeghi X-SW-Source: 2003-05/txt/msg01970.txt.bz2 List-Id: The following reply was made to PR bootstrap/10811; it has been noted by GNATS. From: Dara Hazeghi To: Ari Pollak , gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/10811: libjava/libltdl/configure fails Date: Sat, 17 May 2003 01:54:50 -0700 (PDT) --- Ari Pollak wrote: > Yes, either make bootstrapping or making with > CONFIG_SHELL set to ksh > makes it run fine. What exactly is the difference in > the end result > between 'make' and 'make bootstrap'? Make bootstrap builds the compiler in 3 stages. stage 1: build compiler with existing compiler. stage 2: build compiler with stage 1 compiler stage 3: build compiler with stage 1 compiler (again) final stage: compare the files created in stage 2 and 3, they must be identical! make just does stage 1. theoretically, if make bootstrap works, make should work. But the /bin/sh issues are simply bugs in the Solaris shell, which seem to trigger more or less randomly. CONFIG_SHELL=/bin/ksh is supposed to fix this by providing a reliable shell. Dara P.S. That doesn't mean that it wouldn't be nice to get everything to work with /bin/sh, simply that doing so is difficult, and no one's yet succeeded. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com