> It's not supposed to happen, but it's usually harmless if it does.
> How exactly did you make this happen? Should I just go and try to
> build the latest win32, or do you have a smaller test case?
The only case I have is win32 which is greencard/ffi code and a little
supporting C code. Just from the names of the symbols (i.e., I didn't
look in detail), I think the symbols come from a header file
%#included into the file.
Note that you probably need to update green-card before you start
(Hugs needs it, GHC may not). If you don't do this routinely, the
easiest way to do this is to invoke green-card using an interpreter
(script attached).
And you should use something resembling the make invocation in the
commit message.
--
Alastair
This is the script I use to invoke green-card - much easier than
having to remember to type make all the time. A bit slower than
a ghc build though...
#! /bin/sh
GC_SRC=$HOME/src/green-card/src
# GC_SRC=$HOME/local/gc-2.01/src
RUNHUGS=$HOME/local/bin/runhugs
${RUNHUGS} -c100 -h2m -P${GC_SRC}: GreenCard $*
_______________________________________________
Cvs-hslibs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-hslibs