#10762: On Windows, out-of-codepage characters can cause GHC build to fail ---------------------------------+----------------------------------------- Reporter: snoyberg | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.2 Resolution: | Keywords: Operating System: Windows | Architecture: x86_64 (amd64) Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: ---------------------------------+----------------------------------------- Comment (by rwbarton): To what extent do you consider your suggestions Windows-specific? Since GHC assumes that input Haskell files are always UTF-8, one could argue that `-ddump-to-file` output should always be UTF-8 as well, on every system. However producing UTF-8-encoded console output when the locale specifies a different encoding makes no sense to me, so I hope that suggestion at least is for Windows only.
The workaround we've implemented in stack for now is setting the codepage to 65001 for the console while running stack. This is not ideal, since this is essentially a global setting for the entire console.
It must be my lack of experience with Windows, but I don't understand why this is considered a "workaround" rather than a basic necessity for having any kind of working system. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10762#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler