From: voi dfoo <void.foo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65727@debbugs.gnu.org
Subject: bug#65727: 30.0.50; Build failure in MSYS2 when --with-native-compilation
Date: Mon, 4 Sep 2023 08:42:40 -0700 [thread overview]
Message-ID: <CAN9m-kj+PPaC_=2w6A8uqKLmPOw=7YZFAvK5D3Gso_nKcCzRDg@mail.gmail.com> (raw)
In-Reply-To: <838r9m5dgb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
The dependency versions are not explicitly specified in my installation
script
"pacman -S --needed --noconfirm git zip base-devel
mingw-w64-x86_64-autotools mingw-w64-x86_64-toolchain
mingw-w64-x86_64-xpm-nox mingw-w64-x86_64-libtiff mingw-w64-x86_64-giflib
mingw-w64-x86_64-libpng mingw-w64-x86_64-libjpeg-turbo
mingw-w64-x86_64-librsvg mingw-w64-x86_64-libwebp mingw-w64-x86_64-lcms2
mingw-w64-x86_64-gnutls mingw-w64-x86_64-jansson mingw-w64-x86_64-libgccjit
mingw-w64-x86_64-libxml2 mingw-w64-x86_64-gnutls mingw-w64-x86_64-zlib
mingw-w64-x86_64-harfbuzz mingw-w64-x86_64-tree-sitter
mingw-w64-x86_64-sqlite3"
There is a update of the package to gcc 13.2.0 that may be related:
https://github.com/msys2/MINGW-packages/commits/master/mingw-w64-gcc
On Mon, Sep 4, 2023, 5:29 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: voi dfoo <void.foo@gmail.com>
> > Date: Sun, 3 Sep 2023 22:06:41 -0700
> >
> > Occasionally I use appveyor/GitHub Actions to build Emacs for Windows
> > using MSYS environment. At some point the build started to fail when
> > making .elc files.
> >
> > I suspect that newer version of dependencies (libgccjit?) caused the
> > crash because a previous passing commit now also failed.
> >
> > I don't have a local environment to investigate further. I don't know
> > whether the following information is actionable but here they are
>
> Did you per chance upgrade GCC and/or libgccjit and/or Binutils
> between the last successful build and the first failed one?
>
[-- Attachment #2: Type: text/html, Size: 2130 bytes --]
next prev parent reply other threads:[~2023-09-04 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 5:06 bug#65727: 30.0.50; Build failure in MSYS2 when --with-native-compilation voi dfoo
2023-09-04 12:29 ` Eli Zaretskii
2023-09-04 15:42 ` voi dfoo [this message]
[not found] ` <handler.65727.B.16938191423648.ack@debbugs.gnu.org>
2023-09-21 6:27 ` bug#65727: Acknowledgement (30.0.50; Build failure in MSYS2 when --with-native-compilation) voi dfoo
2023-09-21 8:23 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2023-05-08 8:16 bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation Arash Esbati
2023-06-27 19:28 ` Cyril Arnould
2023-06-27 20:22 ` Andrea Corallo
2024-05-14 19:52 ` Cyril Arnould
2024-05-14 20:33 ` bug#63365: bug#65727: 30.0.50; Build failure in MSYS2 when --with-native-compilation Andrea Corallo
2024-05-14 23:29 ` Cyril Arnould
2024-05-15 6:38 ` Andrea Corallo
2024-05-15 16:35 ` Cyril Arnould
2024-05-15 17:09 ` bug#63365: " Andrea Corallo
2024-05-15 18:45 ` Cyril Arnould
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN9m-kj+PPaC_=2w6A8uqKLmPOw=7YZFAvK5D3Gso_nKcCzRDg@mail.gmail.com' \
--to=void.foo@gmail.com \
--cc=65727@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).