From: "Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 65836-done@debbugs.gnu.org
Subject: bug#65836: 30.0.50; compiling emacs 30.0.50 fails
Date: Tue, 24 Oct 2023 09:48:01 +0200 [thread overview]
Message-ID: <4FBF1C68-A455-412E-AEEF-D0A8CB0F4285@me.com> (raw)
In-Reply-To: <CADwFkm=S8U565qSLguOxXZwyf_C-krULKywuhtNxDyG=HFtZtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3683 bytes --]
Hello,
It is still not working, and I wrote sep 9:
Dear Eli,
The build-script is at https://algon.dk/_doc/build.zsh
and the whole log file at https://algon.dk/_doc/Emacs-build-2023-09-09c.log
I don’t think I made any changes in the build-file since last succes compilation at 2023-08-19
med venlig hilsen (with kind regards)
Niels
I just tried again, and it still comes out with:
sed -n -e '/0xc940/,$ p' < ../../etc/charsets/BIG5.map | awk -f ./big5.awk ) > ../../etc/charsets/BIG5-2.map
cp mapfiles/MULE-ethiopic.map ../../etc/charsets/MULE-ethiopic.map
cp mapfiles/MULE-ipa.map ../../etc/charsets/MULE-ipa.map
cp mapfiles/MULE-is13194.map ../../etc/charsets/MULE-is13194.map
cp mapfiles/MULE-sisheng.map ../../etc/charsets/MULE-sisheng.map
cp mapfiles/MULE-tibetan.map ../../etc/charsets/MULE-tibetan.map
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
***
*** "make bootstrap" failed with exit status 2.
***
*** You could try to:
*** - run "make extraclean" and run "make" again (or, equivalently, run
*** "make bootstrap configure=default"), to rebuild Emacs with the
*** default configuration options, which might fix the problem
*** - run "git clean -fdx" and run "make bootstrap" again, which might
*** fix the problem if "make bootstrap configure=default" did not
*** !BEWARE! "git clean -fdx" deletes all files that are not under
*** !BEWARE! version control, which means that all changes to such
*** !BEWARE! files will be lost and cannot be restored later
*** - run "make V=1", which displays the full commands invoked by make,
*** to further investigate the problem
*** - report the problem and ask for help by sending an email to
*** bug-gnu-emacs@gnu.org, mentioning at least the build error
*** message, the platform, and the repository revision displayed by
*** "git rev-parse HEAD"
***
make[1]: *** [advice-on-failure] Error 2
make: *** [bootstrap] Error 2
./build.zsh 94,61s user 37,46s system 86% cpu 2:33,56 total
tee Emacs-build-2023-10-23a.log 0,00s user 0,06s system 0% cpu 2:33,63 total
med venlig hilsen
Niels
<about:blank#>
Niels Søndergaard • civilingeniør
Address: Mariehøj 236, 2990 Nivå
Mobile: +45 4052 2789 <tel:%20%20+45%204052%202789>
Website: algon.dk <https://algon.dk/>
Email: niels@algon.dk <mailto:niels@algon.dk>
<about:blank#> <about:blank#>
Liberty means responsibility. That is why most men dread it.
— Georg Bernhard Shaw
> Den 23. okt. 2023 kl. 22.04 skrev Stefan Kangas <stefankangas@gmail.com>:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> 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?
>
> More information was requested, but none was given within 6 weeks, so
> I'm closing this bug. If this is still an issue, please reply to this
> email (use "Reply to all" in your email client) and we can reopen the
> bug report.
[-- Attachment #2: Type: text/html, Size: 29218 bytes --]
next prev parent reply other threads:[~2023-10-24 7:48 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
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 [this message]
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=4FBF1C68-A455-412E-AEEF-D0A8CB0F4285@me.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65836-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=solengen@me.com \
--cc=stefankangas@gmail.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).