From: John Fitzpatrick <fitzpat@telus.net>
To: gcc-help@gcc.gnu.org
Subject: Unable to bootstrap compiler.
Date: Thu, 14 Jul 2005 21:58:00 -0000 [thread overview]
Message-ID: <1121378612.10158.65.camel@mayday.fcc.com> (raw)
Hello all,
I am having a problem when I try to bootstrap the compiler. Following
is a typescript that demonstrates the problem. Here is some background
information:
Output of uname -a:
Linux mayday 2.6.5-7.111-default #1 Wed Oct 13 15:45:13 UTC 2004 i686
i686 i386 GNU/Linux
Output of gcc --version for version of gcc I am trying to bootstrap:
gcc (GCC) 4.1.0 20050528 (experimental)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Typescript showing the problem:
Script started on Thu 14 Jul 2005 02:53:56 PM PDT
johnfi@mayday:~/gcc> make bootstrap
make[1]: Entering directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/libiberty'
make[2]: Entering directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/libiberty/testsuite'
make[1]: Leaving directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/libiberty'
make[1]: Entering directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/fixincludes'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/home/johnfi/gcc/build-i686-pc-linux-gnu/fixincludes'
make[1]: Entering directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/intl'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/intl'
make[1]: Entering directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libiberty'
make[2]: Entering directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libiberty/testsuite'
make[1]: Leaving directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libiberty'
make[1]: Entering directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libcpp'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/libcpp'
make[1]: Entering directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/zlib'
true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-g -O2 " "CXXFLAGS=-g -O2"
"CFLAGS_FOR_BUILD=" "CFLAGS_FOR_TARGET=-O2 -g -O2 "
"INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644"
"INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install
-c" "LDFLAGS=" "LIBCFLAGS=-g -O2 " "LIBCFLAGS_FOR_TARGET=-O2 -g -O2 "
"MAKE=make" "MAKEINFO=/home/johnfi/gcc/missing makeinfo
--split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh"
"EXPECT=expect" "RUNTEST=runtest" "RUNTESTFLAGS="
"exec_prefix=/home/johnfi/devel" "infodir=/home/johnfi/devel/info"
"libdir=/home/johnfi/devel/lib" "prefix=/home/johnfi/devel"
"tooldir=/home/johnfi/devel/i686-pc-linux-gnu" "AR=ar" "AS=as" "CC=gcc"
"CXX=c++" "LD=ld" "LIBCFLAGS=-g -O2 " "NM=nm" "PICFLAG=" "RANLIB=ranlib"
"DESTDIR=" DO=all multi-do # make
make[1]: Leaving directory
`/home/johnfi/gcc/host-i686-pc-linux-gnu/zlib'
Bootstrapping the compiler
make[1]: Entering directory `/home/johnfi/gcc/gcc'
make[1]: *** No rule to make target `bootstrap'. Stop.
make[1]: Leaving directory `/home/johnfi/gcc/gcc'
make: *** [bootstrap] Error 2
johnfi@mayday:~/gcc>
Script done on Thu 14 Jul 2005 02:54:10 PM PDT
Obviously the problem is that the makefile doesn't have the target
"bootstrap" in it. Is this a bug?
Thank you in advance for any help.
Sincerely,
John Fitzpatrick
next reply other threads:[~2005-07-14 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 21:58 John Fitzpatrick [this message]
2005-07-14 22:30 ` John Carter
2005-07-15 20:55 ` John Fitzpatrick
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=1121378612.10158.65.camel@mayday.fcc.com \
--to=fitzpat@telus.net \
--cc=gcc-help@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: link
Be 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).