This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/12396] build of gcc 3.4 20030920 fails during compilation of fixincl.c
- From: "p dot van-hoof at qub dot ac dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Sep 2003 22:29:02 -0000
- Subject: [Bug bootstrap/12396] build of gcc 3.4 20030920 fails during compilation of fixincl.c
- References: <20030924233337.12396.p.van-hoof@qub.ac.uk>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12396
------- Additional Comments From p dot van-hoof at qub dot ac dot uk 2003-09-25 22:29 -------
Subject: Re: build of gcc 3.4 20030920 fails during
compilation of fixincl.c
I was obviously thinking the wrong way around there...
In that case the following is relevant. The gcc configure script had problems
further upstream. This is one example out of several:
checking for direct.h... grep: can't open conftest.out
yes
looking in the config.log, I found this:
configure:3077: checking for direct.h
configure:3087: $gcc -E conftest.c >/dev/null 2>conftest.out
/scratch/pvh/temp/gcc/gcc/configure: $gcc: not found
This problem leads to the erroneous conclusion that direct.h is present on the
system. This means that an attempt will be made to include the file in the
mkdir test further downstream. That fails of course, leading to the erroneous
conclusion that mkdir takes one argument. I have attached the complete
config.log.