On Thu, 8 May 2025 at 17:01, Bruno Haible <br...@clisp.org> wrote: > Hi Reuben, > > Reuben Thomas wrote: > > ... > > The problem appears to be that INSTALLDIR is passed to the compiler on > the > > command line, and something in the mingw64 machinery says "aha! it's a > > path!" and transforms it to Windows style. > > Yes, this is the same problem for which I am writing in the INSTALL.windows > file of all packages that I maintain: >
I am not using MSYS2 per se, I am using the Mingw64 environment, i.e. the shell called "MSYS2 MinGW x64" in the MSYS2 64-bit set of shells. My reading of the documentation was that the command-line argument translation should only happen in MSYS2 "proper", so I was surprised that it was happening in the MinGW shell. AFAIU, MSYS_NO_PATHCONV=1 is the workaround for old (defunct) MSYS and > MSYS2_ARG_CONV_EXCL=* is the workaround for MSYS2. See > https://www.msys2.org/wiki/Porting/#filesystem-namespaces I had already read this, and it doesn't seem to correspond to the behaviour I find I get. I think the best action will be to document that the 'relocatable' modules > are not supported in MSYS2 as build environment. > That would be good too, but doesn't seem to be relevant to me, unless I'm misunderstanding what MSYS2 "is"; should I be installing something else instead to build in a "pure" MinGW environment? When I look up MinGW these days I seem to be directed to the msys2.org site and the installer there, and having selected the MinGW x64 terminal from the launchers it installs, I do indeed seem to be in a mingw64 environment…specifically, $ echo $MSYSTEM MINGW64 -- https://rrt.sc3d.org
