Re: How to build ghci?

2003-02-24 Thread Duncan Coutts
On Mon, 24 Feb 2003 09:25:02 + (GMT)
Andre Rauber Du Bois <[EMAIL PROTECTED]> wrote:

> > ghci reports:
> > ghc-5.04.2: not built for interactive use
> > 
> 
>   If you want to have ghci you have to compile the source code with 
> the same version of ghc that you are trying to generate, in your case 
> ghc-5.04.2...

Thank's very much Andre. Now that I look for it, I did find this in the FAQ.
(I looked at the building guide but missed the FAQ!)

I'm still confused however. I though that with the whole two (three?)
stage bootstraping process you get a version of ghc built with itself
anyway, no? Maybe the ghc gurus could enlighten us. :-)

If it requires an extra time consuming step, could it be a ./configure
option? --enable-ghci

Duncan
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: GHCi-5.04.2: Windows Open with ... problem.

2003-02-24 Thread Simon Marlow
> Will this release include the -odir fix (the one for 
> hiearchical names)?

I'm afraid not.  That part of the compiler has changed a lot relative to the 5.04.x 
branch, the fix is non-trivial, and I don't feel confident making that kind of change 
at this stage of the release cycle.  "Better the devil you know".

Using make instead of --make, and explicit -o options instead of -odir, should let you 
workaround the problem.

Cheers,
Simon
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: identifying a raise_closure from C

2003-02-24 Thread Simon Marlow

> In C, I have an StgClosure pointer, pointing to a THUNK.
> 
> I would like to know whether this particular THUNK is a raise_closure,
> (as built by raisezh_fast() in rts/Exception.hc).
> 
> Is there any identifying information I can use to tell 
> definitely whether
> this THUNK is a raise_closure? Perhaps the stg_raise_info info table
> has enough information?

Since raise closures don't have their own closure types, the only way is
to compare the closure's info pointer against stg_raise_info.  This is
fine, and we use the same technique in several other places in the RTS.

Cheers,
Simon
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: How to build ghci?

2003-02-24 Thread Andre Rauber Du Bois

Hello,

> ghci reports:
> ghc-5.04.2: not built for interactive use
> 

If you want to have ghci you have to compile the source code with 
the same version of ghc that you are trying to generate, in your case 
ghc-5.04.2...

Cheers,
Andre.


> Is there anything special I have to do to enable ghci? Is there
> something odd / missing from Mandrke's build environment?
> 
> Duncan
> ___
> Glasgow-haskell-users mailing list
> [EMAIL PROTECTED]
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
> 

-- 
-
André Rauber Du Bois
dubois at macs.hw.ac.uk
http://www.macs.hw.ac.uk/~dubois/

___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


identifying a raise_closure from C

2003-02-24 Thread Bernard James POPE
Hi all,

In C, I have an StgClosure pointer, pointing to a THUNK.

I would like to know whether this particular THUNK is a raise_closure,
(as built by raisezh_fast() in rts/Exception.hc).

Is there any identifying information I can use to tell definitely whether
this THUNK is a raise_closure? Perhaps the stg_raise_info info table
has enough information?

Thanks heaps,
Bernie. 
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users