On Tue, May 03, 2005 at 06:57:23PM -0400, Liwen Huang wrote:
However, when I execute the last command of cross-compilation, I get another problem.
$make hc-file-bundle Project=Ghc I have following error msg. ------------------------------------------------------------- echo ghc-6.4/libraries/base/GHC/PrimopWrappers.hs >> hc-files-to-go echo ghc-6.4/ghc/compiler/parser/Parser.hs >> hc-files-to-go echo ghc-6.4/ghc/compiler/parser/ParserCore.hs >> hc-files-to-go echo ghc-6.4/ghc/compiler/main/ParsePkgConf.hs >> hc-files-to-go echo ghc-6.4/libraries/haskell-src/Language/Haskell/Parser.hs >> hc-files-to-go tar czf ghc-6.4-i386-pc-nto-qnx6.2.0-hc.tar.gz `cat hc-files-to-go` tar: ghc-6.4/ghc/rts/AutoApply_thr.hc: Cannot stat: No such file or directory tar: ghc-6.4/ghc/rts/AutoApply_thr_p.hc: Cannot stat: No such file or directory tar: ghc-6.4/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 -------------------------------------------------------------
I was getting the following while porting ghc-6.4-branch to GNU/Hurd: #v+ $ make hc-file-bundle Project=Ghc [...] echo ghc-6.4/ghc/compiler/main/ParsePkgConf.hs >> hc-files-to-go echo ghc-6.4/libraries/haskell-src/Language/Haskell/Parser.hs >> hc-files-to-go tar czf ghc-6.4-i386-unknown-gnu-hc.tar.gz `cat hc-files-to-go` tar: ghc-6.4/ghc/rts/AutoApply_thr_p.hc: Cannot stat: No such file or directory tar: ghc-6.4/ghc/rts/AutoApply_thr.hc: Cannot stat: No such file or directory tar: ghc-6.4/ghc/rts/AutoApply_debug.hc: Cannot stat: No such file or directory tar: ghc-6.4/libraries/haskell-src/Language/Haskell/Parser.hs: Cannot stat: No such file or directory tar: Error exit delayed from previous errors make: *** [hc-file-bundle] Error 2 #v-
Since it is mentioned in the documentation, that we can ignore "rts error", and the gz file is successfully generated. I decide to try the next step. It it safe to do so?
I continued with the incomplete tarball of .hc files and didn't have any problems related to that (AFAICT), apart from having to unpack happy-1.15/happy into the build tree and run 'make -C happy boot all' before continuing the build. Regards, Thomas