Definitely a bug, the in-place runghc should properly use the in-place compiler. Not sure when it regressed though, but it wouldn't be surprising if this has been happening for a while. On Tue, Dec 8, 2015 at 5:19 PM, Ryan Scott wrote:

Actually, this might not be Windows-related at all. It turns out that runghc was failing because there wasn't a ghc.exe located in inplace/bin (just ghc-stage1.exe and ghc-stage2.exe). Adding a ghc.exe symlink to ghc-stage2.exe made runghc.exe work correctly.

Is this a bug, or the intended behavior?

Ryan S.

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/