runghc should give an error when the path to ghc is invalid
|Reported by:||monoidal||Owned by:||igloo|
|Type of failure:||Incorrect warning at compile-time||Difficulty:||Unknown|
|Test Case:||T7859||Blocked By:|
runghc has a -f option which allows to specify the path to GHC. However, it uses rawSystem and if the path is incorrect, we only get a nonzero exit code. For example, attempting to use "ghc -fdefer-type-errors X.hs" gives absolutely no output.
Attached patch uses findExecutable and gives an error message if the executable is not found. This is not the ideal solution, but I think it's better than the current state.
Change History (6)
Changed 11 months ago by monoidal
comment:3 Changed 10 months ago by igloo
- Milestone set to 7.8.1
- Owner igloo deleted
- Status changed from patch to new