| Some parts of the configuration mechanism changed. Did you invoke
| autoheader and autoconf before configure?
| I didn't either, I didn't even know about autoheader though I
| suppose I should
| have worked it out from Makefile.config. Perhaps a README
| file that actually
| gave correct
My name's Jesse and I'm starting first year computer science this year.
Our first language is Haskell, which we study for about 6 weeks. Before
classes start I and a few friends are trying to get a handle on haskell.
We've each tried using your compiler with no luck.
I have some experience
[ admin note: forwarding to [EMAIL PROTECTED]: Folks, please
don't use glasgow-haskell-{bugs,users}@dcs.gla.ac.uk. I've asked the
Glasgow admins to either disable or redirect the old lists several times,
but until this happens they continue to be connected to an old version of
the mailing
ghc-4.06 distribution lacks the configure script in the ghc subdir.
Running autoconf in ghc subdir fixes the problem.
I know, I noticed this over the weekend. I'll put up a fixed src dist
today, sorry for the inconvenience.
Cheers,
Simon
The mentioned function has 1001 hardwired in one place instead of
using the size parameter.
BTW, why isn't it called in the Haskell convention: memoSized?
Thanks; fixed.
Cheers,
Simon
Simon Peyton-Jones wrote:
To be fair the 'how to build' notes do say "run autoconf first".
I don't think autoheader is necessary. (If it is, someone say so,
in which case it should get added to the build notes.)
It *was* necessary to run autoheader after I've changed acconfig.h
to
Sven Panne wrote:
Simon Peyton-Jones wrote:
To be fair the 'how to build' notes do say "run autoconf first".
I don't think autoheader is necessary. (If it is, someone say so,
in which case it should get added to the build notes.)
It *was* necessary to run autoheader after I've
Hi!
Thanks for your answer. I must confess I hadn't read the Release Notes for
version 4.06. (I was too excited to try GranSim.) However, I had this same
problem with version 4.04. I downloaded it, installed it, it work fine
for a sequential program, but I couldn't compile the tests in
Hi,
It seems that FFI no longer accepts "ByteArray Int" in ghc 4.06 (it
does in ghc 4.04), it looks intentional ? If so, is there another
way to pass a String to a C function ? If not, I have attached
a small example, to see the result do:
tar -xf abc.tar
make
The result should be:
OK. Simon will implement this shortly.
| -Original Message-
| From: George Russell [mailto:[EMAIL PROTECTED]]
| Sent: 31 January 2000 11:20
| To: Sven Panne
| Cc: GHC Bugs
| Subject: Re: FFI.lhs
|
|
| Sven Panne wrote:
|
| Simon Peyton-Jones wrote:
| To be fair the 'how to build'
Hello there,
A make all from CVS failed because of the following:
/usr/local/bin/ghc -cpp -fglasgow-exts -Rghc-timing -I. -IcodeGen -InativeGen -Iparser
Sven Panne [EMAIL PROTECTED] writes:
[ Cross-mailed to ghc-users, too, because this is not really a bug ]
Jan Kort wrote:
It seems that FFI no longer accepts "ByteArray Int" in ghc 4.06
(it does in ghc 4.04), it looks intentional ?
Even it is unintentional now, it will be omitted in
Sigbjorn Finne wrote:
Really? 'ByteArray Int' (and its mutable companion) is still
available, but only if the user can guarantee that the 'import'ed
call does not end up causing a GC, i.e., the following should work
foreign import unsafe splat :: ByteArray Int - IO ()
the "unsafe" bit
13 matches
Mail list logo
