From: Madhu <enometh@meer.net>
To: emacs-devel@gnu.org
Subject: Re: obscure compilation error with cl-defstruct &aux boa constructor
Date: Mon, 18 Apr 2022 08:14:06 +0530 [thread overview]
Message-ID: <m3a6cjyutl.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: jwvtuarzrem.fsf-monnier+emacs@gnu.org
* Stefan Monnier <jwvtuarzrem.fsf-monnier+emacs @gnu.org> :
Wrote on Sun, 17 Apr 2022 11:16:30 -0400:
> Madhu [2022-04-16 22:16:18] wrote:
[...]
>> (stack (make-list (1+ (car ppss)) nil))) 0 4)
>
> It looks like some frames are missing between these two.
I think I posted the full backtrace, but there was other cruft on HEAD,
so it is not the same error you'd get on master with the single
indicated change. which would be
#+begin_example
Loading /dev/shm/emacs/lisp/progmodes/prog-mode.el (source)...
Loading /dev/shm/emacs/lisp/emacs-lisp/lisp-mode.el (source)...
Eager macro-expansion failure: (void-function cl-subseq)
Eager macro-expansion failure: (void-function cl-subseq)
Symbol’s function definition is void: cl-subseq
make[1]: *** [Makefile:912: bootstrap-emacs.pdmp] Error 255
#+end_example
>> The error goes away if I remove the &aux (and thus make all the
>> arguments optional)
>
> I must say that seeing your backtrace I can't understand why your code
> doesn't work or rather why our code works (the call to `cl-subseq`
> depends on the presence of `&aux` which is already present in our code).
>
>> Might this be a bug from a recent change? (I've not looked at the
>> changes yet, so this is a note to self)
>
> The bootstrap is delicate and ad-hoc.
> Sometimes innocuous changes can break it.
I see it isn't a recent error. to compile the indicated form I had a
workaround in loadup.el that defined cl-subseq (after loading "simple"),
since around 2019-03-14. (somehow I'd lost that workaround this time
around)
prev parent reply other threads:[~2022-04-18 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 16:46 obscure compilation error with cl-defstruct &aux boa constructor Madhu
2022-04-17 15:16 ` Stefan Monnier
2022-04-18 2:44 ` Madhu [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3a6cjyutl.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.