There are multiple reasons for abandoning MSYS 1.0 as supported compile platform, in favor of MSYS2.
- Testsuite is guaranteed to fail. There are 2 issues here:
- MSYS 1.0 bash simply won’t work with non-ASCII path, which
is listed as a test case in
rifiuti2. All such paths are treated as ‘No such file or directory’. Same problem has been observed on MSYS2 untilg_win32_get_command_line()call is used. - Some test cases mysteriously fail, but the difference of result inspected with bare eye seems identical. Apparently there is some discrepancy of new line characters at work — it is not an issue on Linux / Unix, but problem will be very observable on Windows.
- MSYS 1.0 bash simply won’t work with non-ASCII path, which
is listed as a test case in
- There was no more update for MSYS / MinGW32 since 2012. Not a fatal sin, but if there is any problem, I have to maintain everything and fix manually. And that’s not a reproduceable development environment.
- No 64-bit support. It is possible to compile both 32 and 64-bit binaries with MSYS2, but old version is 32-bit only.
Four years later: Looks like MinGW + MSYS has a new home and moving again (e.g. 64-bit support) since 2018, but it’s too little too late now.