From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: Eli Zaretskii <eliz@gnu.org>,
74530@debbugs.gnu.org, Osama Rebach <osamarebach@gmail.com>
Subject: bug#74530: 31.0.50; Emacs fails to compile cape package
Date: Mon, 25 Nov 2024 22:24:11 -0500 [thread overview]
Message-ID: <jwvr06yn0hl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87jzcqvj7i.fsf@melete.silentflame.com> (Sean Whitton's message of "Tue, 26 Nov 2024 10:10:09 +0800")
> Stefan's commit a0f60293d9 says
>
> `byte-compile-macro-environment` contains definitions which expand
> to code that is only understood by the rest of the byte-compiler, so
> using it for code which isn't being byte-compiled leads to errors
> such as references to non-existing function
> `internal--with-suppressed-warnings`.
>
> So it sounds like we are inappropriately tangling with machinery
> internal to the byte compiler. I used with-suppressed-warnings in a
> completely standard way, so I think the most likely thing is that we
> have uncovered a bug in the byte compiler, probably something to do with
> evaluating top-level forms while compiling. Adding Stefan.
My guess is that it's the `when-let` inside an `eval-and-compile` that's
making us bite the dust.
I'd welcome a patch to fix that problem, but in the mean time a
patch that actually fixes `when-let` to not use `if-let` (and hence not
use `with-suppressed-warnings` either) might be a simpler solution.
Stefan
next prev parent reply other threads:[~2024-11-26 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 15:07 bug#74530: 31.0.50; Emacs fails to compile cape package Osama Rebach
2024-11-25 15:58 ` Eli Zaretskii
2024-11-26 2:10 ` Sean Whitton
2024-11-26 3:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-27 2:37 ` Sean Whitton
2024-11-27 10:01 ` Osama Rebach
2024-11-27 11:36 ` Sean Whitton
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=jwvr06yn0hl.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74530@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=osamarebach@gmail.com \
--cc=spwhitton@spwhitton.name \
/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).