public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jdx at o2 dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111170] New: Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library) Date: Sun, 27 Aug 2023 11:54:27 +0000 [thread overview] Message-ID: <bug-111170-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111170 Bug ID: 111170 Summary: Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library) Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl CC: costas.argyris at gmail dot com Target Milestone: --- Target: i686-w64-mingw32 @ Windows XP Build: i686-w64-mingw32 @ Windows 10 I wanted to build gcc 13.2 with intention to run it on an old Windows XP/Pentium-M machine. My build environment is MSYS2/MinGW32 @ Windows 10. Everything went fine and I could run resulting binaries on the build machine under MinGW32 terminal. However when I tried to run them on the target machine, I got "bash: ./mingw-gcc/bin/gcc: Accessing a corrupted shared library". After a few days of heavy fight I found out that this is due to malformed manifest embedded in some (not all!) gcc executables. Newer version of Windows are more forgiving and can tolerate malformed manifests while Windows XP is not; that's why I could run freshly built gcc on my Windows 10 box. Using a resource editor I have replaced malformed manifests with a default one (taken from https://packages.msys2.org/base/mingw-w64-windows-default-manifest) and now everything runs fine on XP. The malformed manifest comes from https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=d11e088210a551235d3937f867ee1c8b19d02290 related to PR108865. I think the proper solution is to merge default manifest from MSYS and the one mentioned in the diff above.
next reply other threads:[~2023-08-27 11:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-27 11:54 jdx at o2 dot pl [this message] 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 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@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: linkBe 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).