Subject: bug#75939: bug in compile wrapper when using MSVC from Msys2

From: Kirill Makurin <[email-masked]>
Date: Fri, 31 Jan 2025 09:25:55 +0000

Keep in mind that if this variable is appended to, each item must be separated by a semicolon. Something like this:

```
if test -n "${MSYS2_ARG_CONV_EXCL}"
then
      MSYS2_ARG_CONV_EXCL="${MSYS2_ARG_CONV_EXCL};-Tp"
else
      MSYS2_ARG_CONV_EXCL='-Tp'
fi
export MSYS2_ARG_CONV_EXCL
```

- Kirill Makurin

________________________________
From: Andrew W. Nosenko <[email-masked]>
Sent: Friday, January 31, 2025 4:49 PM
To: Karl Berry <[email-masked]>
Cc: [email-masked] <[email-masked]>; [email-masked] <[email-masked]>
Subject: Re: bug#75939: bug in compile wrapper when using MSVC from Msys2

What if user set this variable for some reasons like additional extra flags? So, it need to add flags to variable, not override it completely, at least.

Sent from mobile

On Fri, 31 Jan 2025 at 00:53, Karl Berry <[email-masked]<mailto:[email-masked]>> wrote:
Hi Kirill - thanks for the report and proposed fix.

    export MSYS2_ARG_CONV_EXCL='-Tp'

Setting an environment variable seems fairly safe, since if an older
version of the compiler doesn't pay attention to it, at least the
problem will not become worse.

However, I'd like to hear from others who use msys, cl, Windows, etc.
(Since I don't), as to whether setting this in the compile script would
cause any problems. Anyone? --thanks, karl.