Re: [wxhaskell-users] announce: wxHaskell 0.9.4, windows bug fix release

[Daan L. <da...@cs...>]

Hi Claus,

Claus Reinke wrote:
>>- wxWidgets make install didn't copy all of the include files
>>    to the installation directory (just copying the one file mentioned
>>    on the wxHaskell building page seems to be sufficient, but I still
>>    wonder what is going on there)
> 
> ah, there are several of them, a pair for each platform, of which only
> one is copied. but this is an _old_ _stable_ release! why hasn't it
> been patched?

No sane person builds wxWidgets with "make & mingw" on a windows platform :-)

(and thus, it becomes a low priority issue for the wxWidgets people)

>>.. But "make dist" fails for wxHaskell, with what 
>>seems to be a cygwin problem:
>>
>>C:\cygwin\bin\bash.exe (2124): *** fork: can't reserve memory for stack 0x40000 - 0x240000, Win32 error 487
>>      5 [main] bash 1584 fork_parent: child 2124 died waiting for longjmp before initialization
>>/bin/bash: fork: No such file or directory
>>make: *** [wxc-dist] Error 129
> 
> 
> updating cygwin didn't help. but slowing down the process revealed
> another error hidden behind this one, namely execvp complaining about
> too long a commandline. and if I do "make dist -n", I'm not really
> surprised about that complaint - have you ever looked at the things
> you're building there with your nice makefile function library?-)

Ah, I had this problem in another library of me.. You are right,
the command line will be way too long. Thanks for pointing this out,
I'll put it on the TODO list.

> ps. oh, the build with 6.5 on winxp works (thoroughly tested 
>     using wx/BouncingBalls;-), although 6.5 still has some issue
>     when running under bash, so one has to run ghci under cmd
>     instead.. it seems others have already seen that in their own
>     builds, but I didn't want to leave the error message issue 
>     open on the list.

That is good to know. Thanks.
-- Daan.