finding .o

[Simon Marlow]

> ghc-5.00.1 -interactive  (binary, linux, i386-unknown)
> 
> forgets sometimes of existing  Foo.o  module to load and loads 
> instead the interpreted code.
> A strange effect. 
> Compiled and loaded is a single module  Foo.hs  in the current 
> directory.
> In such cases I compile  Foo.hs  once more, rerun  ghci, 
> and then it finds  Foo.o.
> How to trace this down if the effect is not always reproducible?

I found one bug recently which could cause this, if you have recursive
modules and use .hi-boot files.  

If this isn't the case, you can get more info using the -ddump-hi-diffs
option, which should give some clue as to why GHC thinks the module
needs to be recompiled.

Cheers,
	Simon