logo       

RE: GHC doesn't doesn't clean up the way it should: msg#00010

lang.haskell.glasgow.bugs

Subject: RE: GHC doesn't doesn't clean up the way it should

Yep, the temporary file is still there. The funny thing is that this doesn't
happen with all files. In my little test case with two Haskell modules only
one of them gets a temp file left behind. What more information can I give
to help you track this one down?

Thanks for the pointer to the documentation!

/Josef

-----Original Message-----
From: Simon Marlow [mailto:simonmar@xxxxxxxxxxxxx]
Sent: den 5 maj 2004 15:33
To: Josef Svenningsson; glasgow-haskell-bugs@xxxxxxxxxxx
Subject: RE: GHC doesn't doesn't clean up the way it should

On 05 May 2004 13:09, Josef Svenningsson wrote:

> Hi again,
>
> Here's a mini-bug.
>
> I'm playing around with adding preprocessors to GHC. I'm using the
> flags -F and -pgmF for that. Since these are not terribly well
> documented I wanted to run with -v to see what happens. This showed
> the following:
>
> *** Haskell pre-processor
> trharp TestHarp.hs TestHarp.hs
> c:\DOCUME~1\JOSEFS~1\LOKALA~1\Temp\ghc2708.hspp
> ...
> *** Deleting temp files
> Deleting: c:/DOCUME~1/JOSEFS~1/LOKALA~1/Temp/ghc2708.hc
> Warning: deleting non-existent
> c:/DOCUME~1/JOSEFS~1/LOKALA~1/Temp/ghc2708.hc
>
>
> Seems like GHC didn't remember the suffix of the file to delete.

Does it really leave the temporary file behind? I tried it here and it
deleted the file.

> This happens with 6.2.1.
>
> I also would like some more documentation on -F. Why does it send the
> program to be mangled twice to the pre-processor for instance?

The syntax of the command line is documented under the -pgmF option,
which you may have missed because -pgmF is documented in two places (I
just fixed that). See here:

http://www.haskell.org/ghc/docs/latest/html/users_guide/options-phases.h
tml#PRE-PROCESSOR

Cheers,
Simon


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise