public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/8657: No rule to make target `bootstrap' in directory 'gcc' Date: Sat, 30 Nov 2002 10:26:00 -0000 [thread overview] Message-ID: <20021121063601.7164.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-11-21 6:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-30 10:26 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-30 17:56 Andris Pavenis 2002-11-30 14:06 Zack Weinberg 2002-11-30 11:36 Neil Booth 2002-11-30 9:26 Rolf-Alois Walter 2002-11-29 2:27 Zack Weinberg 2002-11-28 16:08 Neil Booth 2002-11-28 14:01 bangerth 2002-11-28 13:36 reichelt 2002-11-28 8:02 rolf-alois.walter
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021121063601.7164.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).