From: Pierre Sarrazin <sarrazip@sympatico.ca>
To: gdb@sources.redhat.com
Subject: No rule to make target `gcc'
Date: Wed, 04 Dec 2002 19:32:00 -0000 [thread overview]
Message-ID: <20021204223405.A2645@localhost> (raw)
I've just checked out the HEAD sources from CVS (about 2:00 UTC on
Dec. 5) and the compilation fails this way:
checking for working const... (cached) yes
creating ./config.status
creating Makefile
cd spu && make "CC=gcc" "CFLAGS=-g -O2" "AR=ar" "AR_FLAGS=rc" "AS=as" "CROSS_CFLAGS=" "TARGET_CFLAGS=" "INCLUDES=" all
make[2]: Entering directory `/home/ps/extcvs/gdb/src/utils/spu'
gcc -c -I. -I.././spu -I.././spu/config -I.././spu/../../include -g -O2 .././spu/spu.c
gcc -g -O2 -o spu spu.o
make[2]: Leaving directory `/home/ps/extcvs/gdb/src/utils/spu'
make[1]: Leaving directory `/home/ps/extcvs/gdb/src/utils'
make: *** No rule to make target `gcc', needed by `i686-pc-linux-gnu/libiberty/multilib.out'. Stop.
I checked out 'src', then ran ./configure with only a --prefix option,
then ran make.
My system:
RedHat 7.2
gcc 2.96-112.7.2
glibc 2.2.4-31
libstdc++ 2.96-112.7.2
libtool 1.4.2-7.ximian.1
'which gcc' returns /usr/bin/gcc;
'/usr/bin/gcc --version' returns 2.96.
--
Pierre Sarrazin <sarrazip at sympatico dot ca>
reply other threads:[~2002-12-05 3:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021204223405.A2645@localhost \
--to=sarrazip@sympatico.ca \
--cc=gdb@sources.redhat.com \
/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