source-only release candidate
Several useful changes and fixes have accumulated since the last release (Nov 2003). To get these to a wider audience, I intend to do a source-only release soon. The first release candidate is at: http://cvs.haskell.org/Hugs/downloads/Sep2003/hugs98-Sep2003-rc1.tar.gz Instructions (after unpacking): cd hugs98-Sep2003/src/unix ./configure cd .. make LibStatus grep ERROR LibStatus This builds in-place. 'make install' installs in /usr/local; to install at home, add --prefix=$HOME to the configure line. Other configure options you might try are: --enable-hopengl include HOpenGL, a Haskell binding for OpenGL/GLUT --with-pthreads build Hugs using pthreads C library The old options --enable-readline and --enable-ffi are no longer needed. Please report bugs to hugs-bugs@haskell.org
* Ross Paterson
Several useful changes and fixes have accumulated since the last release (Nov 2003). To get these to a wider audience, I intend to do a source-only release soon.
FreeBSD users can use the Port skeleton: http://people.freebsd.org/~obraun/pending_ports/hugs-Sep2003-rc1.tar.gz The diff against the current lang/hugs directory is available from: http://people.freebsd.org/~obraun/pending_ports/hugs-Sep2003-rc1.diff Regards, Olli -- Oliver Braun -- obraun @ { unsane.org | FreeBSD.org | haskell.org }
Hi Ross, | Several useful changes and fixes have accumulated since the | last release (Nov 2003). To get these to a wider audience, I | intend to do a source-only release soon. The first release | candidate is at: | http://cvs.haskell.org/Hugs/downloads/Sep2003/hugs98-Sep2003-rc1.tar.gz Although I was able to build and run it on Redhat 9, I couldn't get it to work on Windows. I ran into a number of problems when I tried to build it on Windows using cygwin. An hour later or two later, I did eventually manage to get it to compile, but then I couldn't get it to run and successfully load the prelude. After some attempts to debug it, time forced me to abandon the attempt. I thought I'd try it again this evening using the msc compiler. That was a little easier (I only had to fix one problem before it compiled), but again I couldn't get it to run. 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. All the best, Mark 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). (I'm not at all convinced the other changes I made were correct or effective, so I'll spare you the details.)
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.
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
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'"
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
On Thu, Sep 25, 2003 at 01:42:49PM -0700, David Bakin wrote:
Did not build the fptools - do I need to?
Oh yes, this is now essential for the Prelude, the standard libraries and many others besides. (This accounts for problems 2 and 3.) The conversion must be done in a Unix-like environment like cygwin or mingw. You will need to have built runhugs and ffihugs. You need to move into src and say mkdir -p ../hugsdir/tools ../hugsdir/include ../hugsdir/libraries/Hugs cp ../tools/* ../hugsdir/tools cp HsFFI.h config.h unix/MachDeps.h unix/template-hsc.h ../hugsdir/include cp ../libraries/Hugs/*.* ../hugsdir/libraries/Hugs cd unix ./convert_libraries ../../fptools ../../hugsdir env HUGSDIR=../../hugsdir HUGSFLAGS='' ./BuildFFI You will then need the directories ../hugsdir/libraries and ../hugsdir/oldlib (or copies of them) in your Hugs search path.
w.r.t. fptools - can you explain what I need here. The first line seems to
be running happy over parser.y - but I thought there was already an
up-to-date good parser.c in src. The second line seems to be running a
program called hsc2hs - which is in the ghc distribution - but it appears to
be doing unix-ish stuff. How do I build the fptools for win32? A lot of the
makefiles seem ghc-specific. I guess the issue is that I'm willing to try
this out on win32 (esp. as I didn't see anyone else say they're trying it)
but I'm unfamilar with the tree. I do have cygwin & ghc 5.02 installed if
they are necessary to build hugs.
-- Dave
from toplevel makefile:
find fptools/libraries -name "*.ly" -o -name "*.y" | xargs -l happy
find fptools/libraries -name "*.hsc" | xargs -l hsc2hs --no-compile
find fptools/libraries -name "*_hsc_make.c" | xargs src/unix/hsc_kludge
-- Dave
----- Original Message -----
From: "'Ross Paterson'"
On Thu, Sep 25, 2003 at 01:42:49PM -0700, David Bakin wrote:
Did not build the fptools - do I need to?
Oh yes, this is now essential for the Prelude, the standard libraries and many others besides. (This accounts for problems 2 and 3.)
The conversion must be done in a Unix-like environment like cygwin or mingw. You will need to have built runhugs and ffihugs. You need to move into src and say
mkdir -p ../hugsdir/tools ../hugsdir/include ../hugsdir/libraries/Hugs cp ../tools/* ../hugsdir/tools cp HsFFI.h config.h unix/MachDeps.h unix/template-hsc.h ../hugsdir/include cp ../libraries/Hugs/*.* ../hugsdir/libraries/Hugs cd unix ./convert_libraries ../../fptools ../../hugsdir env HUGSDIR=../../hugsdir HUGSFLAGS='' ./BuildFFI
You will then need the directories ../hugsdir/libraries and ../hugsdir/oldlib (or copies of them) in your Hugs search path.
On Thu, Sep 25, 2003 at 04:46:55PM -0700, David Bakin wrote:
w.r.t. fptools - can you explain what I need here. The first line seems to be running happy over parser.y - but I thought there was already an up-to-date good parser.c in src. The second line seems to be running a program called hsc2hs - which is in the ghc distribution - but it appears to be doing unix-ish stuff. How do I build the fptools for win32? A lot of the makefiles seem ghc-specific. I guess the issue is that I'm willing to try this out on win32 (esp. as I didn't see anyone else say they're trying it) but I'm unfamilar with the tree. I do have cygwin & ghc 5.02 installed if they are necessary to build hugs.
The top-level Makefile is used to build source distributions (like the one you have) and Red Hat packages -- you don't need it. You also don't need the Makefiles inside fptools. The library modules inside fptools in a source package have already been preprocessed with happy and hsc2hs, so you don't need those (or ghc) to build Hugs. You will however need cygwin to run the commands that convert the fptools libraries. But on second thoughts the steps I gave won't work, because they need some files created by configure. I think you need to do what's in src/unix/README, except that there are more generated files now than when that was written. So my next suggestion is cd src/unix ../msc/config.sh cd .. make
Regarding building on Windows: what is missing are the libraries, which need to be converted from the fptools ones useing a shell script, after running configure. I expect that this is possible, and possibly easy, under Cygwin, but I don't know how to do it. As a partial stopgap, I've placed a conversion of most of the libraries (but not including the Win32 libraries) at http://cvs.haskell.org/Hugs/downloads/Sep2003/libs.tar.gz That contains the directories libraries and oldlib, which need to be in your {Hugs} directory. To use the FFI, you'll need to compile Hugs.Storable, as follows: ffihugs +G -P +L../libraries/Hugs/Storable_aux.c Hugs.Storable
Oh boy, thanks, I"ll try that this evening -- Dave
----- Original Message -----
From: "'Ross Paterson'"
Regarding building on Windows: what is missing are the libraries, which need to be converted from the fptools ones useing a shell script, after running configure. I expect that this is possible, and possibly easy, under Cygwin, but I don't know how to do it. As a partial stopgap, I've placed a conversion of most of the libraries (but not including the Win32 libraries) at
http://cvs.haskell.org/Hugs/downloads/Sep2003/libs.tar.gz
That contains the directories libraries and oldlib, which need to be in your {Hugs} directory.
To use the FFI, you'll need to compile Hugs.Storable, as follows:
ffihugs +G -P +L../libraries/Hugs/Storable_aux.c Hugs.Storable
participants (5)
-
'Ross Paterson' -
David Bakin -
Mark P Jones -
Oliver Braun -
Ross Paterson