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] Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library)
Date: Sun, 27 Aug 2023 14:56:53 +0000	[thread overview]
Message-ID: <bug-111170-4-iYbMr9aIwJ@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 #2 from LIU Hao <lh_mouse at 126 dot com> ---
(In reply to Costas Argyris from comment #1)
> Looks like '... @ Windows XP' is the Host, not the Target, in the PR.   
> Target seems irrelevant here.
> 
> LH, is this the issue you originally mentioned about my change inadvertently
> replacing the default MSYS2 manifest?

It looks like that the current GCC manifest contains values that their host
does not support. In theory it should be ignored; however if it causes errors,
it might be worth looking into.

The MSYS2 manifest contains a `compatibility` section that is not supported by
XP and Vista and is ignored [1], so it has no effect.


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

  parent reply	other threads:[~2023-08-27 14:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-27 11:54 [Bug target/111170] New: " 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 [this message]
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
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-iYbMr9aIwJ@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).