
Hi, When building 6.10.1 under Macports, I notice that hpc now requires that hsc2hs be present on the system (it does not use the hsc2hs built in place with the new ghc). Previous versions did not require hsc2hs to be present; the compiler could be bootstrapped from just the ghc compiler and ghc-pkg. The hpc library is the only one that requires the external hsc2hs. Is this new dependency intentional, or is this a build system bug? This problem escaped detection initially because cabal will use any hsc2hs on the path even if the --with-compiler flag is set. (--with-compiler forces a particular compiler and packaging program, but not hsc2hs.) This is just asking for trouble. For the moment, it's fixed in the Macports build by hacking hpc's Makefile to specify --with-hsc2hs. Should cabal produce and error or a warning if hsc2hs is not found in the same directory as the compiler? I suggest an error by default, but not if --with- hsc2hs is given explicitly. Best Wishes, Greg

On Wed, 2008-11-12 at 12:39 -0500, Gregory Wright wrote:
Should cabal produce and error or a warning if hsc2hs is not found in the same directory as the compiler? I suggest an error by default, but not if --with-hsc2hs is given explicitly.
I don't think so. In principle hsc2hs is not tied to ghc, it just happens to be shipped with it. The versions do not need to match up (much). It's in the same category as other pre-processors like c2hs. For the ghc build system, either it really does need an external hsc2hs in which case it should detect it in the top level configure script or it can use the one it ships with in which case it should be using the --with-hsc2hs flag. Duncan
participants (2)
-
Duncan Coutts
-
Gregory Wright