From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21695 invoked by alias); 21 Nov 2002 08:16:02 -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 21659 invoked by uid 71); 21 Nov 2002 08:16:01 -0000 Date: Sat, 30 Nov 2002 17:56:00 -0000 Message-ID: <20021121081601.21658.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andris Pavenis Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc' Reply-To: Andris Pavenis X-SW-Source: 2002-11/txt/msg01201.txt.bz2 List-Id: The following reply was made to PR bootstrap/8657; it has been noted by GNATS. From: Andris Pavenis To: Neil Booth , Zack Weinberg 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: Thu, 21 Nov 2002 10:11:42 +0200 On Thursday 21 November 2002 08:50, Neil Booth wrote: > Zack Weinberg wrote:- > > > 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. > > For nearly 3 years I have used > > ../configure --enable-languages=whatever --prefix=whatever > > and it works fine. I think a '~' in prefix used to always work, but > that broke recently in libstdc++. I also up to recently used similar directory layout for building GCC for target i586-pc-msdosdjgpp (build directory was subdirectory of source one and I run configure using relative path). With GCC-3.2 I found that I'm getting trouble with 'make -C gcc gnatlib_and_tools'. Moving build directory out of source one fixed problem and I'm using relative path to configure (like ../gcc-3.2/configure ....). So my experience shows that simple moving build directory from build.djg to ../build.gcc relative to source directory fixed build failure with building gnatlib and Ada tools. I didn't study this problem more detailed though. I remember trying something similar under Linux and getting the same problem, but I may be wrong. This was really only problem with build directory being subdirectory of source directory I have noticed up to this time. Andris