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: 26 Sep 2003 19:21:17 -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-26 19:21 -------
Subject: Re: build of gcc 3.4 20030920 fails during
compilation of fixincl.c
> Did you set the CC environment variable to anything?
No.
It seems the problems are already starting during the configure of libiberty.
When I look through the config.log for libiberty (under "Cache variables"), I
find that all variables with embedded spaces (i.e. all variables that need to be
quoted) have an extra $. So the problem is not limited to ac_cv_prog_CPP alone.
I have uploaded the file. This suggest that something is going wrong when the
variables are written out to file.