From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Bradley Lucier <lucier@math.purdue.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap failure configuring in-tree gmp in mainline
Date: Sat, 25 Jul 2009 11:18:00 -0000 [thread overview]
Message-ID: <20090725111805.GF2985@gmx.de> (raw)
In-Reply-To: <1247690276.4172.20.camel@frying-pan>
* Bradley Lucier wrote on Wed, Jul 15, 2009 at 10:37:56PM CEST:
> After configuring
>
> Target: x86_64-unknown-linux-gnu
> gcc version 4.5.0 20090715 (experimental) [trunk revision 149654] (GCC)
>
> with
>
> ../../mainline/configure --enable-checking=release --prefix=/pkgs/gcc-mainline-mem-stats --enable-languages=c --enable-gather-detailed-mem-stats
>
> I get the bootstrap error:
>
> Configuring stage 2 in ./gmp
> < stuff omitted>
> checking how to run the C++ preprocessor... /lib/cpp
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> make[2]: *** [configure-stage2-gmp] Error 1
> make[2]: Leaving directory `/home/lucier/programs/gcc/objdirs/mainline'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/home/lucier/programs/gcc/objdirs/mainline'
> make: *** [bootstrap] Error 2
>
> This is using an in-tree gmp 4.3.0, gmp/config.log reports:
>
> configure:11030: checking how to run the C++ preprocessor
> configure:11061: /home/lucier/programs/gcc/objdirs/mainline/./prev-gcc/g++ -B/home/lucier/programs/gcc/objdirs/mainline/./prev-gcc/ -B/pkgs/gcc-mainline-mem-stats/x86_64-unknown-linux-gnu/bin/ -nostdinc++ -I/home/lucier/programs/gcc/objdirs/mainline/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/home/lucier/programs/gcc/objdirs/mainline/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/lucier/programs/gcc/objdirs/mainline/../../mainline/libstdc++-v3/libsupc++ -L/home/lucier/programs/gcc/objdirs/mainline/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs -E -DNO_ASM conftest.cc
> /home/lucier/programs/gcc/mainline/gmp/configure: line 11062: /home/lucier/programs/gcc/objdirs/mainline/./prev-gcc/g++: No such file or directory
> <stuff omitted>
> configure:11061: /lib/cpp -DNO_ASM conftest.cc
> cpp: error trying to exec 'cc1plus': execvp: No such file or directory
>
> Am i missing something?
Does /home/lucier/programs/gcc/objdirs/mainline/./prev-gcc/g++ exist,
and if yes, is it a functioning executable?
If it doesn't exist, that looks like the toplevel logic for which
languages to build still has a loop hole for --enable-languages=c,
either not properly enabling the C++ compiler for stage 1, or wrongly
overriding CXX, CXX_FOR_BUILD in toplevel Makefile.tpl to point to
nonexistent previous-stage C++ compiler. I don't know which is the
desired one.
BTW, what's the last <stuff omitted>, and why does your /lib/cpp try to
spawn cc1plus?
Cheers,
Ralf
next prev parent reply other threads:[~2009-07-25 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:38 Bradley Lucier
2009-07-25 11:18 ` Ralf Wildenhues [this message]
2009-07-25 16:47 ` Bradley Lucier
2009-07-25 16:54 ` Paolo Bonzini
2009-07-25 18:16 ` Bradley Lucier
2009-07-25 18:18 ` Bradley Lucier
2009-07-25 18:26 ` Paolo Bonzini
2009-08-06 8:42 ` Bradley Lucier
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=20090725111805.GF2985@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc@gcc.gnu.org \
--cc=lucier@math.purdue.edu \
/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).