From: Eli Z. <el...@gn...> - 2012-02-25 07:47:15
|
> From: "Sisyphus" <sis...@op...> > Date: Sat, 25 Feb 2012 18:14:26 +1100 > > From: "Eli Zaretskii" > > > The "Syntax error" _is_ the clue, IMO. I think it actually says that > > cpp is the cause of the problem. Can you tell which cpp.exe is being > > picked up by GCC > > Can that be determined by running 'which cpp.exe' ? > Or is it possible that 'gcc' and 'which' each pick up a different cpp.exe ? Anything's possible. The way to know is to use the -v switch to GCC, as I suggested in my message. But first, I suggest that you try reproducing the same failure you see in config.log, with the same test program, running GCC from the shell prompt. That should tell you whether the problem is with cpp.exe or with something that only rears its ugly head when the MSYS Bash runs the configure script. |