Simon,
I have figured out what our problem is , and it the age old favorite RTFM. I
had compiled our library code as usual, but was compiling up the rest of the
code with -prof. As it quite clearly states in the manual I need to compile
all modules, so I agree with ghc --make and those library modules do need
recompiling!
thanks for the reply anyway!
..andy (for Chris)
> set of libraries
> that we build and install in a shared area and then use with
> ghc --make. The
> problem is that ghc then (sometimes) tries to rebuild the
> libraries: something
> that is doomed to fail for a variety of reasons.
>
> (We think that it might be prone to do this if it doesn't
> have write permission
> for the library .hi and .o files.)
>
> Why would ghc do this? Nothing has changed in the libraries
> obviously, and the
> libraries are quite self-contained, not referring back to
> anything else that has changed.
This isn't supposed to happen. However, finding a test case might be a
different matter. Can you give us any more clues? If it decides to
recompile a library module, does it do that repeatedly? Can you send us
the output from 'ghc --make -v4 -ddump-rn-trace' when it happens.
What version of GHC is this, BTW?
> We don't build the libraries with ghc --make, itself but use
> a makefile.
>
> Would it be possible/sensible to provide a means of telling
> ghc --make not to
> try and rebuild any modules in a given directory?
The mechanism we have for doing this is packages. GHC will never try to
recompile anything in another package. To work around you problem you
could make a package out of the library (this is recommended anyhow),
but we'd still like to track down the recompilation problem.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
