From: Eli Zaretskii <eliz@gnu.org>
To: Loreno Heer <helohe@bluewin.ch>
Cc: emacs-devel@gnu.org
Subject: Re: MinGW build on master fails with Error 127
Date: Mon, 12 Dec 2022 18:11:39 +0200 [thread overview]
Message-ID: <83r0x4r490.fsf@gnu.org> (raw)
In-Reply-To: <01b7362d-7d60-3054-5590-d4dbbcda76d7@bluewin.ch> (message from Loreno Heer on Mon, 12 Dec 2022 17:03:32 +0100)
> Date: Mon, 12 Dec 2022 17:03:32 +0100
> Cc: emacs-devel@gnu.org
> From: Loreno Heer <helohe@bluewin.ch>
>
> > Which parts of MinGW got updated? Did Make get updated? or Bash?
>
> [2022-12-12T12:35:19+0100] [PACMAN] Running 'pacman -Syuu'
> [2022-12-12T12:35:19+0100] [PACMAN] synchronizing package lists
> [2022-12-12T12:35:36+0100] [PACMAN] starting core system upgrade
> [2022-12-12T12:37:14+0100] [ALPM] transaction started
> [2022-12-12T12:37:16+0100] [ALPM] upgraded bash (5.1.016-1 -> 5.2.009-1)
[...]
So basically, lots of stuff was updated including Bash. Who knows
what that could cause?
Are you able to build the source tarball of Emacs 28.2?
Do you have an anti-virus installed? if so, can you turn it off, or
temporarily disable it, and try again?
> $ ./temacs --batch -l loadup --temacs=pbootstrap --bin-dest
> /mingw64/bin/ --eln-dest /mingw64/lib/emacs/30.0.50/
>
> User@UserPC MINGW64 ~/src/emacs/src
> $ echo $?
> 127
So it isn't Make, probably. But it still could be Bash, or some of
the libraries that Emacs links in.
next prev parent reply other threads:[~2022-12-12 16:11 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 [this message]
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
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=83r0x4r490.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=helohe@bluewin.ch \
/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).