MSYS2 update (those who build on Windows please read)
Hi Windows devs, February comes with a major change in behavior for MSYS2/Cygwin. Tools such as awk/sed etc now use binary mode unless on a text mount: https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html This is problematic because GHC etc only use the underlying OS to determine how to output line endings. As such we output \r\n but in sed et al $ will no longer match line endings. Which means out scripts are currently broken. Do not upgrade your MSYS2 install until a workaround for this is in place or you will be unable to compile GHC. If you have updated your MSYS2 then using a text mount may be the easiest option to get a working build again. As it seems just downgrading the tools alone is not enough. Thanks, Tamar
Hi all,
MSYS2 maintainers have agreed that the change by Cygwin constitudes a
regression for the MSYS2 project and patched out the changes.
It's now safe to upgrade MSYS2 again.
Tamar
On Mon, Feb 20, 2017 at 3:58 PM, Phyx
Hi Windows devs,
February comes with a major change in behavior for MSYS2/Cygwin. Tools such as awk/sed etc now use binary mode unless on a text mount: https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html
This is problematic because GHC etc only use the underlying OS to determine how to output line endings. As such we output \r\n but in sed et al $ will no longer match line endings. Which means out scripts are currently broken.
Do not upgrade your MSYS2 install until a workaround for this is in place or you will be unable to compile GHC.
If you have updated your MSYS2 then using a text mount may be the easiest option to get a working build again. As it seems just downgrading the tools alone is not enough.
Thanks, Tamar
participants (1)
-
Phyx