Preparing a Registered hc-file-bundle (Was Bootstrapping withHC files)

[Simon Marlow]

On 13 December 2005 18:58, Andrew Walrond wrote:

> Well, I gave it a blast anyway. All went well creating the hc files
> until the last command:
> 
>> 	$ make hc-file-bundle Project=Ghc
> 
> at which point it failed with
> 
> tar czf ghc-6.4.1-x86_64-unknown-linux-hc.tar.gz `cat hc-files-to-go`
> tar: ghc-6.4.1/ghc/rts/AutoApply_thr.hc: Cannot stat: No such file or
> directory
> tar: ghc-6.4.1/ghc/rts/AutoApply_thr_p.hc: Cannot stat: No such file
> or directory
> tar: ghc-6.4.1/ghc/rts/AutoApply_debug.hc: Cannot stat: No such file
> or directory
> tar: Error exit delayed from previous errors
> make: *** [hc-file-bundle] Error 2

Yes, these are harmless.  They are caused by the fact that AutoApply.cmm
is auto-generated in several different ways (AutoApply_thr.cmm,
AutoApply_debug.cmm etc.), and the .hc files for these are named
AutoApply_thr.thr_hc, AutoAPply_debug.debug_hc, and so on.  The Makefile
code for hc-bundle doesn't know about this special case.

> Googling suggests this might be harmless, so I tried bootstrapping on
> the target machine using the created tarball, but that failed with
> 
> /bin/ld: cannot find -lghccompat
> collect2: ld returned 1 exit status
> make[1]: *** [stage1/ghc-6.4.1] Error 1
> make: *** [all] Error 1
> make: Leaving directory
> `/home/andrew/test/ghc/bs/target/ghc-6.4.1/ghc' 

Please send us a full log of the build.  libghccompat.a should be in
ghc/lib/compat, and it should be built quite early on.

Cheers,
	Simon