unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: 53675@debbugs.gnu.org
Subject: bug#53675: lisp/startup.el; startup--require-comp-safely async compile breaks if comp is required in init
Date: Tue, 01 Feb 2022 11:01:15 +0000	[thread overview]
Message-ID: <xjffsp2x344.fsf@ma.sdf.org> (raw)
In-Reply-To: <CA+G3_POSQHkO6dBuXSxKgZF2GcKwbZp+tx1rbRyKva2QEsoD_g@mail.gmail.com> (Tom Gillespie's message of "Mon, 31 Jan 2022 20:13:22 -0800")

Tom Gillespie <tgbugs@gmail.com> writes:

> async compilation no longer runs on startup if comp
> is required during loading of user init files
>
> The issue is from 536a57b72ce11b1bb8d1b34b339424fea6ccbcce
> Fix potential native compiler circular dependencies during load
>
> If for whatever reason during the loading of a user init file
> the feature 'comp is loaded (e.g. because they have a call to
> (use-package queue) in init.el), then startup will not honor
> delayed native compilations. Known causes are cases where
> (require 'comp) is called directly in an init file, or where
> any comp autoload is reached e.g. if a builtin such as
> macroexpand is advised during init re: bug#47049.

Hi Tom,

thanks for reporting and debugging this issue.

a92c6191b0 should fix this, could ou please have a try?

Thanks

  Andrea






  reply	other threads:[~2022-02-01 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  4:13 bug#53675: lisp/startup.el; startup--require-comp-safely async compile breaks if comp is required in init Tom Gillespie
2022-02-01 11:01 ` Andrea Corallo [this message]
2022-02-01 12:44   ` Arash Esbati
2022-02-01 15:36     ` Andrea Corallo
2022-02-01 16:51       ` Andrea Corallo
2022-02-01 18:05         ` Arash Esbati
2022-02-02  5:24         ` Tom Gillespie
2022-02-02  9:12           ` Andrea Corallo

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=xjffsp2x344.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=53675@debbugs.gnu.org \
    --cc=tgbugs@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).