From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47161@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
akrl@sdf.org
Subject: bug#47161: 28.0.50; [feature/native-comp] Failure to native-compile bytecomp.el etc.
Date: Fri, 24 Jun 2022 15:18:50 +0200 [thread overview]
Message-ID: <87o7yinqrp.fsf@gnus.org> (raw)
In-Reply-To: <83a6qzdux4.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Mar 2021 17:28:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Can you try and reproduce this while `macroexp--debug-eager` is set to
>> a non-nil value so we hopefully get a backtrace?
>
> Sorry, it stopped happening for me, so I cannot reproduce this
> anymore.
It's been a year, and this still works fine, so I guess it went away for
real, and I'm therefore closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-06-24 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:27 bug#47161: 28.0.50; [feature/native-comp] Failure to native-compile bytecomp.el etc Eli Zaretskii
2021-03-15 15:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-15 17:26 ` Eli Zaretskii
2021-03-15 20:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 12:50 ` Eli Zaretskii
2021-03-16 16:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:29 ` Eli Zaretskii
2021-03-17 1:27 ` Stefan Monnier
2021-03-19 15:28 ` Eli Zaretskii
2021-03-19 15:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 16:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 13:18 ` Lars Ingebrigtsen [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
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=87o7yinqrp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47161@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).