Re: HEAD build fails on OS X

3 Apr 2013

      Hi Austin,

I didn't have much time to look into the problem, but I did run the last
command (the one that fails) and it outputs this when run with 'sh -x':

sh -x gen_contents_index --verbose
+ set -e
+ USAGE='Usage: gen_contents_index [--intree] [--verbose] [--help]'
+ INTREE=
+ VERBOSE=
+ HADDOCK_ARGS=
+ '[' 1 -ne 0 ']'
+ case "$1" in
+ VERBOSE=yes
+ shift
+ '[' 0 -ne 0 ']'
+ '[' -n '' ']'
+ HADDOCK=../../../../../bin/haddock
++ grep -v '/ghc\.haddock'
++ sort
++ ls -1 '*/*.haddock'
ls: */*.haddock: No such file or directory
+ HADDOCK_FILES=
+ HADDOCK_ARGS='-p prologue.txt'
+ '[' -n yes ']'
+ echo -p prologue.txt
-p prologue.txt
+ ../../../../../bin/haddock --gen-index --gen-contents -o . -t 'Haskell
Hierarchical Libraries' -p prologue.txt
gen_contents_index: line 80: ../../../../../bin/haddock: No such file or
directory

So the problem seems to be that the path to haddock in that script is bad
for my setup. I haven't yet tracked down why line 80 in
libraries/gen_contents_index occurs that way. It seems strange to have that
path hardcoded in that way. I guess it might be generated by some earlier
build scripts.

On Wed, Apr 3, 2013 at 1:22 PM, Austin Seipp  wrote:
...
Andreas,
After seeing this, I updated my 'pristine' (unmodified, completely clean)
GHC tree to the latest HEAD, copied the mk/build.mk.sample over my existing
build.mk (since Ian made some changes to it recently,) and HEAD builds
fine for me as of this morning. I'm running the testsuite now...
Specs - OS X Mountain Lion 10.8.3. My HEAD points to
commit 9d33fc3c55fe5f45ebaec5f2031e63813a2ba27a by Ian this morning.
On Wed, Apr 3, 2013 at 9:08 AM, Andreas Voellmy 
...
wrote:
...
I got a fresh copy of HEAD today, and the build failed. The failing
command is:
$ cd libraries && sh gen_contents_index --intree
haddock: internal error:
/Users/andreas/repos/temp-ghc-2/ghc-build/inplace/lib/html/Ocean.std-theme/hslogo-16.png:
copyFile: does not exist (No such file or directory)
I have not yet had time to look into this, but hopefully someone knows
what happened here.
-Andi
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
--
Regards,
Austin - PGP: 4096R/0x91384671