From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: MinGW build on master fails with Error 127
Date: Mon, 26 Dec 2022 15:02:05 +0200 [thread overview]
Message-ID: <837cye2u9e.fsf@gnu.org> (raw)
In-Reply-To: <87sfh3y2z5.fsf@telefonica.net> (message from Óscar Fuentes on Sun, 25 Dec 2022 15:25:50 +0100)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Sun, 25 Dec 2022 15:25:50 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > ** Download and install MinGW-w64 and MSYS2
> >
> > Go to https://msys2.org and follow the instructions. It is not
> > necessary to install the packages suggested on those instructions.
> >
> > What does the last sentence mean? which packages are unnecessary?
> > Some of them, all of them?
>
> The packages mentioned on msys2.org either are the "wrong" ones (UCRT64)
> or are already listed on INSTALL.W64.
So you are saying they should "follow the instructions" up until and
including item 5, and thereafter proceed with what we say in "**
Download and install the necessary packages"?
> > Also, it looks like msys2.org tells users to install the UCRT64
> > variety of MinGW,
>
> Yes, UCRT64 is the variety recommended by the MSYS2 team since recently.
>
> > whereas you said earlier that INSTALL.W64 points to
> > the MSVCRT variety. Should we say something about this in the
> > Download and Install sections?
>
> That's already solved as our instructions direct the user to the MINGW64
> shell and the packages on our list are the mingw-w64-x86_64-* variety.
>
> >> Some problems remain:
> >>
> >> * There are references to past emacs versions.
> >
> > I fixed that, but I honestly don't see how this is important. They
> > are just examples.
>
> The impression I got from that document is that the user will tend to
> type commands verbatim.
>
> >> * libgccjit is missing on the list of dependencies.
> >
> > Please tell how to modify the pacman command to add libgccjit.
>
> Add the package mingw-w64-x86_64-libgccjit.
Got it, thanks.
next prev parent reply other threads:[~2022-12-26 13:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 15:26 MinGW build on master fails with Error 127 Loreno Heer
2022-12-12 15:40 ` Eli Zaretskii
2022-12-12 15:44 ` Loreno Heer
2022-12-12 15:56 ` Eli Zaretskii
2022-12-12 16:03 ` Loreno Heer
2022-12-12 16:11 ` Eli Zaretskii
2022-12-12 16:54 ` Loreno Heer
2022-12-23 21:45 ` Loreno Heer
2022-12-24 6:36 ` Eli Zaretskii
2022-12-24 14:18 ` Loreno Heer
2022-12-24 14:43 ` Eli Zaretskii
2022-12-24 15:11 ` Loreno Heer
2022-12-24 15:44 ` Eli Zaretskii
2022-12-24 22:50 ` Loreno Heer
2022-12-24 15:31 ` Óscar Fuentes
2022-12-24 15:50 ` Eli Zaretskii
2022-12-24 16:14 ` Óscar Fuentes
2022-12-24 16:46 ` Eli Zaretskii
2022-12-24 16:58 ` Óscar Fuentes
2022-12-24 17:08 ` Óscar Fuentes
2022-12-24 17:20 ` Eli Zaretskii
2022-12-24 17:57 ` Óscar Fuentes
2022-12-24 18:09 ` Eli Zaretskii
2022-12-24 18:56 ` Óscar Fuentes
2022-12-24 19:10 ` Eli Zaretskii
2022-12-25 2:46 ` Óscar Fuentes
2022-12-25 8:29 ` Eli Zaretskii
2022-12-25 14:25 ` Óscar Fuentes
2022-12-26 13:02 ` Eli Zaretskii [this message]
2022-12-26 13:33 ` Óscar Fuentes
2022-12-24 19:19 ` Óscar Fuentes
2022-12-24 19:27 ` Eli Zaretskii
2022-12-25 0:13 ` Po Lu
2022-12-25 0:48 ` Óscar Fuentes
2022-12-25 6:46 ` Eli Zaretskii
2022-12-24 18:03 ` Óscar Fuentes
2022-12-24 18:49 ` Eli Zaretskii
2022-12-24 19:23 ` Óscar Fuentes
2022-12-24 19:29 ` Eli Zaretskii
2022-12-24 19:44 ` Óscar Fuentes
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=837cye2u9e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).