unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jschmidt4gnu@vodafonemail.de,  acm@muc.de,  yandros@gmail.com,
	emacs-devel@gnu.org,  luangruo@yahoo.com
Subject: Re: make check produces 25 failures and hangs (bug #65176).
Date: Mon, 14 Aug 2023 09:38:28 -0400	[thread overview]
Message-ID: <yp1il9hbv6z.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83h6p1bzev.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Aug 2023 15:07:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: Jens Schmidt <jschmidt4gnu@vodafonemail.de>,  acm@muc.de,
>>   yandros@gmail.com,  emacs-devel@gnu.org,  luangruo@yahoo.com
>> Date: Mon, 14 Aug 2023 03:51:39 -0400
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >>          (setq native-comp-enable-subr-trampolines t))
>> >>                ^^^^^^^^^^^
>> >
>> >
>> > These two are supposed to be aliases (the comp-enable-subr-trampolines
>> > one is the old name, the other one is the new name).
>> >
>> > If the alias is missing, we should restore it, in addition to fixing
>> > the name we use in startup.el.
>> 
>> Thanks Jens for the analysis and you for the fix.
>> 
>> We have in place the alias, but I guess when the code in loadup is
>> executed is to early and is maybe not effective?
>
> Where is the alias?  I don't think I see it.  What did I miss?

You are right apologies, got confised with the make-obsolete-variable we
have in place.  I added the alias with 922b6490286 in 29.

Should we do the same for `native-comp-deferred-compilation'?

Thanks

  Andrea



  reply	other threads:[~2023-08-14 13:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 19:18 make check produces 25 failures and hangs (bug #65176) Alan Mackenzie
2023-08-10 19:54 ` chad
2023-08-10 20:14   ` Alan Mackenzie
2023-08-10 20:34     ` Alan Mackenzie
2023-08-10 21:54       ` Jens Schmidt
2023-08-11  5:37         ` Eli Zaretskii
2023-08-11 19:39           ` Jens Schmidt
2023-08-12  0:10             ` Po Lu
2023-08-12  9:30               ` Jens Schmidt
2023-08-12 18:03           ` Andrea Corallo
2023-08-12 19:09             ` Andrea Corallo
2023-08-13 10:59               ` Jens Schmidt
2023-08-13 11:34                 ` Alan Mackenzie
2023-08-13 12:07                 ` Eli Zaretskii
2023-08-14  7:51                   ` Andrea Corallo
2023-08-14 12:07                     ` Eli Zaretskii
2023-08-14 13:38                       ` Andrea Corallo [this message]
2023-08-14 13:44                         ` Eli Zaretskii
2023-08-14 14:13                           ` Andrea Corallo
2023-08-14 14:52                         ` Alan Mackenzie

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=yp1il9hbv6z.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=luangruo@yahoo.com \
    --cc=yandros@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).