public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [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
Date: Wed, 15 Nov 2023 12:25:17 +0000	[thread overview]
Message-ID: <bug-111170-4-GOhzzUPYYr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111170-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from LIU Hao <lh_mouse at 126 dot com> ---
(In reply to Costas Argyris from comment #4)
> 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.

I don't think we have declared Windows XP unsupported. There was even an
attempt to maintain Windows 98:
https://www.mail-archive.com/mingw-w64-public@lists.sourceforge.net/msg21399.html

I think the decision is probably we have default as Windows 10 but don't break
old systems by intention, so when someone requests it they get it.


> 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?

https://learn.microsoft.com/en-us/windows/win32/win7appqual/compatibility---application-manifest#manifestation-of-change

```
Applications without a Compatibility section in their manifest will receive
Windows Vista behavior by default on Windows 7 and future Windows versions.
Note that Windows XP and Windows Vista ignore this manifest section and it has
no impact on them.
```

But Microsoft documentation sometimes lies. If Windows XP does not ignore the
manifest and fails instead, we will need a solution.


> 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?

XP was not assigned a UUID because it (2001) predated this manifest thing (2004
or 2005 I guess? since MSVCR80).

  parent reply	other threads:[~2023-11-15 12:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27 11:54 [Bug target/111170] New: Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library) jdx at o2 dot pl
2023-08-27 13:10 ` [Bug target/111170] " costas.argyris at gmail dot com
2023-08-27 14:56 ` lh_mouse at 126 dot com
2023-11-15  6:45 ` [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 lh_mouse at 126 dot com
2023-11-15 11:45 ` costas.argyris at gmail dot com
2023-11-15 12:25 ` lh_mouse at 126 dot com [this message]
2023-11-15 12:59 ` costas.argyris at gmail dot com
2023-11-16 13:59 ` costas.argyris at gmail dot com
2023-11-20 18:54 ` costas.argyris at gmail dot com
2023-11-21  1:13 ` lh_mouse at 126 dot com
2023-11-21  9:43 ` costas.argyris at gmail dot com
2023-11-23  0:49 ` cvs-commit at gcc dot gnu.org
2023-11-23  9:24 ` costas.argyris at gmail dot com
2023-11-28 22:19 ` ebotcazou at gcc dot gnu.org
2023-11-29  9:46 ` costas.argyris at gmail dot com
2023-11-29 10:56 ` cvs-commit at gcc dot gnu.org
2024-01-31 14:32 ` rguenth at gcc dot gnu.org
2024-03-07 23:22 ` law at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111170-4-GOhzzUPYYr@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).