On Thu, Dec 13, 2012 at 7:23 AM, Simon Marlow wrote:
> It is definitely a version problem you have?
If autoreconf picks a gcc binary that is different from the one shipped
with GHC source, that would explain the problem he reported.
Basically the C compiler that is running can't work with GHC's
On Thu, Dec 13, 2012 at 4:30 AM, Simon Peyton-Jones
wrote:
> | Is installing a newer version of msys/mingw an option? The version I
> | have here has autoreconf version 2.68, which I expect would just work.
>
> Interesting. I had assumed that we used autoreconf from inplace/mingw/bin.
> But the
On 13/12/12 12:13, Simon Peyton-Jones wrote:
| > We had all these version-skew problems between MSYS and our build
| > system, which we beautifully resolved by including a tar-ball of
| > guaranteed-compatible msys binaries in the GHC source repo (and GHC
| > distributions). The C compiler is th
| > We had all these version-skew problems between MSYS and our build
| > system, which we beautifully resolved by including a tar-ball of
| > guaranteed-compatible msys binaries in the GHC source repo (and GHC
| > distributions). The C compiler is there, the linker. Why not
| > autoreconf??
|
|
On 13/12/12 10:30, Simon Peyton-Jones wrote:
| Is installing a newer version of msys/mingw an option? The version I
| have here has autoreconf version 2.68, which I expect would just work.
Interesting. I had assumed that we used autoreconf from inplace/mingw/bin.
But there is no autoreconf th
| Is installing a newer version of msys/mingw an option? The version I
| have here has autoreconf version 2.68, which I expect would just work.
Interesting. I had assumed that we used autoreconf from inplace/mingw/bin.
But there is no autoreconf there. So in fact the build system is using it f
On Tue, Dec 11, 2012 at 5:18 AM, Simon Peyton-Jones
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 stu
On Mon, Dec 10, 2012 at 4:19 PM, Simon Peyton-Jones
wrote:
> With a clean build in Windows/MSYS I’m getting lots of autoconf WARNINGS;
> see below.
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?
-- Gaby
With a clean build in Windows/MSYS I'm getting lots of autoconf WARNINGS; see
below.
Simon
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for _LARGE_FILES value needed for large files... no
checking bfd.h usability... no
checking bfd.h presence... yes
configure: WARNI
