From: Andrea Corallo <akrl@sdf.org>
To: Mark Kennedy <mark.t.kennedy@gmail.com>
Cc: 52833@debbugs.gnu.org
Subject: bug#52833: native compilation fails on teco.el from MELPA
Date: Tue, 28 Dec 2021 15:05:15 +0000 [thread overview]
Message-ID: <xjfbl106a8k.fsf@ma.sdf.org> (raw)
In-Reply-To: <CANru7VFCeWnzz4LoLe17_wptKXoGWv5R2eWmqsMXOOFvSnpdDQ@mail.gmail.com> (Mark Kennedy's message of "Mon, 27 Dec 2021 15:40:09 -0500")
Mark Kennedy <mark.t.kennedy@gmail.com> writes:
> from a fresh build:
>
> src/emacs -Q -batch -l comp -f batch-native-compile /home/mtk/.emacs.d/elpa/teco-20200707.2309/teco.el
> Debugger entered--Lisp error: (args-out-of-range "/home/mtk/.emacs.d/elpa/teco-20200707.2309/teco.el" "d" 1)
> signal(args-out-of-range ("/home/mtk/.emacs.d/elpa/teco-20200707.2309/teco.el" "d" 1))
> comp--native-compile("/home/mtk/.emacs.d/elpa/teco-20200707.2309/teco.el")
> batch-native-compile()
> command-line-1(("-l" "comp" "-f" "batch-native-compile" "/home/mtk/.emacs.d/elpa/teco-20200707.2309/teco.el"))
> command-line()
> normal-top-level()
Hi Mark,
having a look here, the trouble is that the compiler is presented with a
function named "teco:type-1-\^M". The ^M is the trigger for the bug
while converting the lisp function name in a valid symbol name for the C
toolchain. The fix should cover all characters below 15 that might
appear in a symbol.
I've installed a fix on master as e7699bf290, please have a look if it
works for you as well.
Maintainers will tell us if we want to backport it on emacs-28 as well
(I think would be worth).
Thanks
Andrea
next prev parent reply other threads:[~2021-12-28 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 20:40 bug#52833: native compilation fails on teco.el from MELPA Mark Kennedy
2021-12-28 15:05 ` Andrea Corallo [this message]
2021-12-28 15:09 ` Lars Ingebrigtsen
2021-12-28 15:21 ` Eli Zaretskii
2021-12-28 19:08 ` Mark Kennedy
2021-12-28 21:37 ` Andrea Corallo
2022-01-15 12:31 ` Lars Ingebrigtsen
2022-01-15 12:46 ` Eli Zaretskii
2022-01-17 10:59 ` Andrea Corallo
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=xjfbl106a8k.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=52833@debbugs.gnu.org \
--cc=mark.t.kennedy@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).