From: Eli Zaretskii <eliz@gnu.org>
To: "Niels Søndergaard" <solengen@me.com>
Cc: 65836@debbugs.gnu.org
Subject: bug#65836: 30.0.50; compiling emacs 30.0.50 fails
Date: Sat, 09 Sep 2023 11:11:31 +0300 [thread overview]
Message-ID: <83h6o3vk98.fsf@gnu.org> (raw)
In-Reply-To: <62E8D3CF-1E12-46F7-9503-FFF993E7D1E6@me.com> (bug-gnu-emacs@gnu.org)
> Date: Sat, 9 Sep 2023 09:54:28 +0200
> From: Niels Søndergaard via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> "
> cp mapfiles/MULE-lviscii.map ../../etc/charsets/MULE-lviscii.map
> cp mapfiles/MULE-uviscii.map ../../etc/charsets/MULE-uviscii.map
> awk -f ./gb180304.awk < ../../etc/charsets/GB180302.map > ../../etc/charsets/GB180304.map
> AWK=awk ./mapconv glibc/EUC-JISX0213.gz '/^<.*[ ]\/x[a-f]/' GLIBC-2-7 \
> | sed -f ./jisx2131-filter \
> | sed -e 's/0x2015/0x2014/' -e 's/0x2299/0x29BF/' > ../../etc/charsets/JISX2131.map
> echo timestamp > charsets.stamp
> make[2]: *** [src] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [actual-bootstrap] Error 2
Any idea which command failed? If you don't know, and if the command
used -j (i.e. parallel execution), please show the complete log of the
build, not just its last part.
And which commit of the master branch did you use to build?
Thanks.
next prev parent reply other threads:[~2023-09-09 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 7:54 bug#65836: 30.0.50; compiling emacs 30.0.50 fails Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 8:11 ` Eli Zaretskii [this message]
2023-10-23 20:04 ` Stefan Kangas
2023-10-24 7:48 ` Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 8:05 ` Gerd Möllmann
2023-10-24 8:56 ` Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 9:03 ` Gerd Möllmann
2023-10-24 8:22 ` Stefan Kangas
2023-10-24 8:34 ` Gerd Möllmann
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=83h6o3vk98.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65836@debbugs.gnu.org \
--cc=solengen@me.com \
/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).