[Bug target/111170] [13/14 regression] Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library) since r13-6552-gd11e088210a551

["costas.argyris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111170

--- Comment #4 from Costas Argyris <costas.argyris at gmail dot com> ---
A couple of comments:

1) Isn't Windows XP officially not supported any more?    If that is the case,
does it make sense to introduce a new configure option solely to deal with an
unsupported host?    I'm not even sure why this is called a regression, given
that it breaks something that is not officially supported.

2) Would it be easier if, instead of excluding the manifest via a new configure
option, we somehow made the manifest file itself smart enough to ignore itself
when running on Windows XP?

Based on your comment above about the compatibility section in the MSYS2
manifest, it sounds like the GCC manifest could get a similar compatibility
section that basically says "ignore this manifest when running on XP (or
earlier)" such that it doesn't break in these old Windows versions.

I searched for the MSYS2 manifest and I think it sources it from cygwin:

https://sourceware.org/git/?p=cygwin-apps/windows-default-manifest.git;a=blob;f=default-manifest.rc;h=2c4ddf4783b953afaf7df9473450bf95842d1911;hb=HEAD

which has separate entries for all the Windows versions, marking them as
'supportedOS'.

Would it be possible to do this in the GCC manifest and solve this problem, or
did I misunderstand how the compatibility section works?