From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9564 invoked by alias); 20 Nov 2002 21:56:01 -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 9547 invoked by uid 71); 20 Nov 2002 21:56:01 -0000 Date: Fri, 29 Nov 2002 02:27:00 -0000 Message-ID: <20021120215601.9546.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Zack Weinberg Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc' Reply-To: Zack Weinberg X-SW-Source: 2002-11/txt/msg01137.txt.bz2 List-Id: The following reply was made to PR bootstrap/8657; it has been noted by GNATS. From: Zack Weinberg To: Neil Booth Cc: reichelt@igpm.rwth-aachen.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rolf-alois.walter@db.com, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc' Date: Wed, 20 Nov 2002 13:46:26 -0800 Neil Booth writes: >> >> First, we highly recommend that GCC be built into a separate >> directory than the sources which does not reside within the >> source tree. This is how we generally build GCC; building where >> srcdir == objdir should still work, but doesn't get extensive >> testing; building where objdir is a subdirectory of srcdir is >> unsupported. > > This latter "unsupported" configuration is what (at least) me and > Jakub build on, and it has *always* worked. Maybe the docs should > be updated. In my experience, if objdir is a subdirectory of srcdir AND configure is invoked by a relative pathname, it doesn't work. But if configure is invoked by an absolute pathname, objdir can happily be a subdirectory of srcdir; and if objdir is not a subdirectory of srcdir, relative paths work fine. I don't remember the exact failure mode, but it was clearly a case of some shell script fragment somewhere getting mixed up about how many ../ components it needed to put in a pathname. zw