Re: Unreliability of the build system

Don't mix in-tree and out-of-tree builds. I *think* I am not mixing them. I'm running builds either in ghc-build (lndired to ghc-working, this often gets blown away) and ghc-validate (these are in-tree builds, cleaned with maintainer-clean). There are no builds in ghc-working.

If you want to use out-of-tree builds, you can eliminate leftover build artifacts from your source tree using 'git ls-files -o' (you'll have to execute this in libraries/*, etc. also to make sure you've got everything). Thanks for the tip, I'll try that.

I'll also try to debug my problem if I find some time. I think this deserves a bug report. Janek

Geoff

On 05/15/2013 08:25 PM, David Terei wrote:

...

I no longer use a separate build dir (i.e., lndir). I switched away

from it as it wasn't buying me anything and I would run into issues that only seemed to manifest with symlinks. Otherwise I've not experienced the issues you mention. I'd point out though that GHC's 'no validate failures' is very frequently violated which did confuse me a lot when getting started.

On 15 May 2013 05:10, Jan Stolarek wrote: > This has never happened to me. I can't even guess why it might

happen to

...

> you.

Looking through the validation log I see that tests fail with

this error message:

...

Actual stderr output differs from expected: --- /dev/null 2013-05-14 15:38:10.771000000 +0200 +++ ../../libraries/base/tests/IO/T3307.run.stderr 2013-05-15

09:21:45.695049002 +0200

...

@@ -0,0 +1,2 @@ +WARNING: cache is out of date:

/dane/uczelnia/projekty/ghc-validate/bindisttest/install

...

dir/lib/ghc-7.7.20130514/package.conf.d/package.cache + use 'ghc-pkg recache' to fix. *** unexpected failure for T3307(normal)

Any ideas why this happens?

Janek