unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Loreno Heer <helohe@bluewin.ch>
To: emacs-devel@gnu.org
Subject: MinGW build on master fails with Error 127
Date: Mon, 12 Dec 2022 16:26:44 +0100	[thread overview]
Message-ID: <tn7h7l$3vk$1@ciao.gmane.io> (raw)

MinGW build on master fails with Error 127:

> make[3]: Leaving directory '/home/User/src/emacs/admin/charsets'
> rm -f bootstrap-emacs.pdmp
> ./temacs --batch  -l loadup --temacs=pbootstrap \
>         --bin-dest /home/User/emacs-master-x86_64-full/bin/ --eln-dest /home/User/emacs-master-x86_64-full/lib/emacs/30.0.50/
> make[2]: *** [Makefile:915: bootstrap-emacs.pdmp] Error 127
> make[2]: Leaving directory '/home/User/src/emacs/src'
> make[1]: *** [Makefile:544: src] Error 2
> make[1]: Leaving directory '/home/User/src/emacs'
> make[1]: Entering directory '/home/User/src/emacs'
> ***
> *** "make all" failed with exit status 2.
> ***
> *** You could try to:
> *** - run "make bootstrap", which might fix the problem
> *** - run "make V=1", which displays the full commands invoked by make,
> ***   to further investigate the problem
> ***
> make[1]: *** [Makefile:414: advice-on-failure] Error 2
> make[1]: Leaving directory '/home/User/src/emacs'
> make: *** [Makefile:370: all] Error 2


I already tried make bootstrap and
git reset --hard and git clean -dxf
with a new build. Still fails.





             reply	other threads:[~2022-12-12 15:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 15:26 Loreno Heer [this message]
2022-12-12 15:40 ` MinGW build on master fails with Error 127 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
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='tn7h7l$3vk$1@ciao.gmane.io' \
    --to=helohe@bluewin.ch \
    --cc=emacs-devel@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).