all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 55194@debbugs.gnu.org
Subject: bug#55194: 29.0.50; Current master fails to bootstrap in the native-compilation configuration
Date: Sat, 30 Apr 2022 16:27:14 +0200	[thread overview]
Message-ID: <87tuaa1wal.fsf@gnus.org> (raw)
In-Reply-To: <E1nkn80-0002B3-Qm@maintain0p.gnu.org> (Eli Zaretskii's message of "Sat, 30 Apr 2022 09:27:16 -0400")

Eli Zaretskii <eliz@gnu.org> writes:

> As Subject says: I cannot bootstrap the current master configure with
> native-compilation on GNU/Linux.  The last part of the build before
> the failure is attached; it seems to have something to do with if-let
> called in files.el, although that code is very old, and if-let is an
> autoloaded macro.  Could this have something to do with the latest
> changes regarding oclosure etc.?

No, I think it's just the usual "don't load subr-x during bootstrap"
problem.  I've now rewritten the offending function.

> P.S. Why do we call macros from subr-x, which is not preloaded, in
> files.el, which _is_ preloaded?

I think that's fine, so long as the subr-x isn't loaded during
bootstrap.  If I remember correctly.

However, I think it's high time that we put the if-let family of macros
into subr.  However, that doesn't seem to be trivial -- I tried now and
that broke bootstrap, too.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-04-30 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 13:27 bug#55194: 29.0.50; Current master fails to bootstrap in the native-compilation configuration Eli Zaretskii
2022-04-30 14:27 ` Lars Ingebrigtsen [this message]
2022-04-30 14:46   ` Lars Ingebrigtsen

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=87tuaa1wal.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55194@debbugs.gnu.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 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.