I have Hugs Sep 2003 rc1 compiling and loading the prelude but I haven't tested it yet beyond that point. My environment is command line usage of VC++ .NET 2003 (but the compiler isn't really the issue), under cmd.exe (not cygwin). This is a preliminary report - in addition to not testing beyond starting it and loading the prelude, I have NOT built runhugs.exe, ffihugs.exe or hugsscript.dll. Changes: 1) CONTEXT changed to CTXT in parser.y, input.c as Mark found. 2) In evaluator.c - remove lines 198-203 in loadPrelude() where is is trying to load STD_PRELUDE_HUGS (Hugs.prelude) which doesn't exist (and wasn't in the Nov 2002 Hugs either...) 3) In msc\options.h insert "{Hugs}\\libraries\\Hugs;" into the HUGSPATH (I put it after the "{Hugs}\\libraries;" element) so Hugs can find the prelude - which is one level down now at libraries\Hugs rather than libraries. 4) In msc\Makefile - well, you can do various things here to the compiler flags. I changed the runtime library option to -MT from -ML. I'm going to test with -RTC1 -GF -GS to see if those new runtime checks catch any problems. There are a couple of warnings when compling (with -W3) - don't know if they're serious yet (haven't looked): builtin.c builtin.c(2191) : warning C4113: 'void (__cdecl *)()' differs in parameter lists from 'void (__cdecl *)(HugsStackPtr,int)' builtin.c(2202) : warning C4113: 'HugsStablePtr (__cdecl *)()' differs in parameter lists from 'HugsStablePtr (__cdecl *)(void)' Did not build the fptools - do I need to? Not sure what additional work I'll be able to do today - but I would like to run a sanity check if you can suggest one. -- Dave Bakin ----- Original Message ----- From: "'Ross Paterson'" <ross@soi.city.ac.uk> To: "Mark P Jones" <mpj@cse.ogi.edu> Cc: <hugs-users@haskell.org> Sent: Thursday, September 25, 2003 2:19 AM Subject: Re: source-only release candidate
On Wed, Sep 24, 2003 at 10:05:11PM -0700, Mark P Jones wrote:
You've mentioned before that you don't have a machine to try doing the windows builds yourself. And I'm afraid I don't have the time (or, it would seem, the technical skill) to do this any more.
Is somebody else looking Windows builds? I was surprised that this "release candidate" doesn't build under Windows, and I'm certainly hoping that this can be fixed in the release.
It's not (just) the lack of a machine -- we don't have anyone with the time and expertise to do it. As near as I can tell no one has done a Windows build for months. It's a miserable situation, but we can't delay a release for non-Windows users forever. Any volunteers would be welcome.
PS. One problem in both the cygwin and msc cases was the use of the symbol "CONTEXT" in parser.y/parser.c and input.c, which clashes with a standard symbol in the windows libraries. I suggest renaming it to CTXT (if you like, PREDICATES is probably available instead).
Thanks, done.
(I'm not at all convinced the other changes I made were correct or effective, so I'll spare you the details.)
Please don't. Anything is better than nothing. _______________________________________________ Hugs-Users mailing list Hugs-Users@haskell.org http://www.haskell.org/mailman/listinfo/hugs-users