bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc'

[Zack Weinberg]

The following reply was made to PR bootstrap/8657; it has been noted by GNATS.

From: Zack Weinberg <zack@codesourcery.com>
To: "Rolf-Alois Walter" <rolf-alois.walter@db.com>
Cc: Neil Booth <neil@daikokuya.co.uk>,  reichelt@igpm.rwth-aachen.de,
	  gcc-bugs@gcc.gnu.org,  gcc-prs@gcc.gnu.org,  nobody@gcc.gnu.org,
	  gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory
 'gcc'
Date: Wed, 20 Nov 2002 22:31:02 -0800

 "Rolf-Alois Walter" <rolf-alois.walter@db.com> writes:
 
 > Hi,
 >
 > For my second try I used the objdir /software/gcc-3.2.1-obj. There I
 > invoked the configure-script with absolute path:
 > /software/gcc-3.2.1/configure 2>&1 | tee configure.out.  Then I did
 > gmake bootstrap 2>&1 | tee gmake.out and still got the error "no
 > rule to make target bootstrap".
 
 Your problem is not caused by the directory layout.  From configure.out:
 
 # Links are now set up to build a native compiler for powerpc-ibm-aix4.3.3.0
 # updating cache ../config.cache
 # creating ./config.status
 # creating Makefile
 # sed: Couldn't re-allocate memory
 # creating intl/Makefile
 # creating fixinc/Makefile
 # creating gccbug
 # creating mklibgcc
 # creating auto-host.h
 
 and gmake.out:
 
 # gmake[1]: Leaving directory `/software/gcc-3.2.1-obj/zlib'
 # Bootstrapping the compiler
 # gmake[1]: Entering directory `/software/gcc-3.2.1-obj/gcc'
 # gmake[1]: *** No rule to make target `bootstrap'.  Stop.
 # gmake[1]: Leaving directory `/software/gcc-3.2.1-obj/gcc'
 
 That sed error message suggests to me that the configure script failed
 to create a complete Makefile in /software/gcc-3.2.1-obj/gcc, so
 naturally the build failed.
 
 Things to try: first, since this is a memory allocation failure, make
 all your resource limits as big as you possibly can, ideally
 'unlimited'.  Later phases of the build will require lots of memory,
 too; you don't want to get past the configure phase only to have the
 compiler die the same way.
 
 Second, it's possible that config.status tickles a bug in AIX sed.
 You could try using GNU sed.
 
 zw