[ ghc-Bugs-231631 ] CompManager confused by not compiled .hs files

noreply@sourceforge.net noreply@sourceforge.net
Mon, 22 Oct 2001 03:59:02 -0700


Bugs item #231631, was opened at 2001-02-08 17:16
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=108032&aid=231631&group_id=8032

Category: Compiler
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Manuel M. T. Chakravarty (chak)
>Assigned to: Simon Marlow (simonmar)
Summary: CompManager confused by not compiled .hs files

Initial Comment:
Version: CVS HEAD from 09/02/2001

When I compile a module 

  import Ptr
  main = print 42

with

  ghc -c -package lang Main.hs

then ghc causes trouble iff I have a file with the name `Ptr.hs' in the current directory.  Instead of using `Ptr'
from -package lang, ghc complains about a missing file `Ptr.hi'.

I can imagine why this is happening and it probably even makes sense for the interactive system; however, it is counter-intuitive for the batch system and diverges from the behaviour of 4.08.

This situation occurs easily in a setup, where I have a version Ptr.hs that my Makefiles arrange to compile in when using 4.08, but omit in favour of the module coming with -package lang when using 4.11.


----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2001-10-22 03:59

Message:
Logged In: YES 
user_id=48280

Fixed.  ghc -c now uses a different module-searching 
algorithm from GHCi; namely, it looks for .hi files only 
whereas GHCi (and ghc --make) looks for source files.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-20 16:49

Message:
Logged In: NO 

This is still present in 5.02, and it does not have to be
the current directory - any directory in the import path
will do.

I will attache a tar file, if SourceForge will let me,
showing how to reproduce the bug in its stronger form. If
SourceForge will not, interested persons may email me for
it.

BTW I could not log-in to SourceForge to submit this, even
though I have a SourceForge account!

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=108032&aid=231631&group_id=8032