> From: Gavin Smith <gavinsmith0...@gmail.com> > Date: Tue, 4 Apr 2023 10:56:28 +0100 > Cc: Eli Zaretskii <e...@gnu.org>, bug-texinfo@gnu.org > > The other thing that I am confused about is that you said you were > building on "Win10, Msys2/MinGW64". Would Msys2 and MinGW64 not > be two different architectures?
Yes. > Is it appropriate to be running (or building) Msys2 programs in an > MinGW64 shell? Yes. It's actually MSYS2' raison d'être. MSYS2 is a set of tools and builds of GNU software intended to allow you to build MinGW programs using Unix shell scripts, Autoconf, and Makefiles that assume Unix shells and Unix semantics. The programs you build using MSYS2 will be MinGW (a.k.a. "native Windows) programs if the compiler and linker you invoke are MinGW compiler and linker. > Mixing two similar but distinct systems could have very confusing results. It _is_ confusing at times (as this discussion clearly shows), but it's a necessary evil: you cannot build GNU and Unix packages on Windows without using MSYS2. > The MSYS2 website tells me they have their own terminal program called > "mintty"; have you tried building or running in that terminal? The problem (at least the problem with Info showing Unicode quotes) is not during the build, it's when Arash runs the Info he produced. That should work first and foremost on the Command Prompt window, which is the native Windows terminal emulator. Whether it also works inside mintty, I don't know, but that could be a separate problem, and making it work would be a bonus, because the MinGW build of Info supports the Command Prompt as its main terminal.
