On Tue, Dec 11, 2012 at 5:18 AM, Simon Peyton-Jones
<simo...@microsoft.com> wrote:
> |  Wild guess:  what does config.log say about your C compiler ans flags
> |  used to invoke it?
> |  Can you post it if it is not too big?
>
> config.log attached.
>
> The build falls over later with the errors below, so I'm totally stuck on 
> Windows.  Help sought!

The build error is a consequence of the configuration error.  For some reason,
the modified gcc.exe driver cannot find the  generated include file.
In fact, the earlier configure warning suggests that the tests can't find
most include files at all.

Now, on the speculation side:
   1.  did you update your C compiler to anything other than GCC 4.5.2?

Looking into driver/gcc/gcc.c, it appears that might be a possible cuase.

>From the config.log, every time the modified gcc.exe is invoked it
returns success (exit code 0) to the shell but it does not appear
to produce any output file.  This confuses Autoconf.  Hence, the
"warning" about file being present but not compilable.  Furthermore,
we don't even have any disganostic message from the pristine
realgcc.exe driver.

-- Gaby

_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to