unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam James <sam@gentoo.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 74490@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	v.pupillo@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#74490: 31.0.50; make bootstrap fails
Date: Sat, 23 Nov 2024 16:37:03 +0000	[thread overview]
Message-ID: <87mshp7vps.fsf@gentoo.org> (raw)
In-Reply-To: <CADwFkmmL__28kuRwuJNwxSO2Eo+7+rCQTkviS1guV2BbwTFZ_w@mail.gmail.com> (Stefan Kangas's message of "Sat, 23 Nov 2024 10:53:24 -0500")

Stefan Kangas <stefankangas@gmail.com> writes:

> close 74490 31.0.50
> thanks
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> So I believe it's a bad idea to use rx in an autoloaded defconst,
>> since we cannot know whether the defconst will be in loaddefs.el
>> before or after the rx macro.
>>
>> Stefan, are there any clean ways of using calls to autoloaded macros
>> in autoloaded defconst or defvar?
>
> I couldn't find a clean way to do that, so I installed a quick
> workaround to avoid having a broken master.  If anyone has a better
> idea, please speak up (or just install it).

Thanks, I can build now.

>
> Meanwhile, I'm closing this bug.





  parent reply	other threads:[~2024-11-23 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23 12:22 bug#74490: 31.0.50; make bootstrap fails Vincenzo Pupillo
2024-11-23 13:44 ` Eli Zaretskii
2024-11-23 14:21   ` Eli Zaretskii
2024-11-23 15:53     ` Stefan Kangas
2024-11-23 16:29       ` Eli Zaretskii
2024-11-23 16:38         ` Eli Zaretskii
2024-11-23 17:04           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 17:36         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 16:37       ` Sam James [this message]
2024-11-23 17:03       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 17:15         ` Stefan Kangas
2024-11-23 14:31   ` Gerd Möllmann

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=87mshp7vps.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=74490@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    --cc=v.pupillo@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).