GNU bug report logs - #49507
28.0.50; macOS: Symbol’s value as variable is void: lock-file-name-transforms

Previous Next

Full log

Message #34 received at 49507 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Naofumi Yasufuku <naofumi <at> yasufuku.dev>
Cc: larsi <at> gnus.org, 49507 <at> debbugs.gnu.org
Subject: Re: bug#49507: 28.0.50; macOS: Symbol’s value as variable is void:
 lock-file-name-transforms
Date: Sun, 11 Jul 2021 09:22:35 +0300

> From: Naofumi Yasufuku <naofumi <at> yasufuku.dev>
> Cc: larsi <at> gnus.org, 49507 <at> debbugs.gnu.org
> Date: Sun, 11 Jul 2021 07:35:46 +0900
> 
> >> Lisp Backtrace:
> >> "write-region" (0xefbfdd58)
> >> "comp-run-async-workers" (0xefbfdf10)
> >> "native--compile-async" (0xefbfe180)
> >> "defalias" (0xefbfe250)
> >> "set-language-environment" (0xefbfeac8)
> >> "set-locale-environment" (0xefbfee88)
> >> "normal-top-level" (0xefbfef30)
> >> (gdb) s
> >> Symbol’s value as variable is void: lock-file-name-transforms
> >
> > Any idea why Emacs needs to native-compile something at startup?
> > Which Lisp file does it native-compile here?
> 
> It seems lisp/language/*-util.el autoloads can invoke this native-compile.

Right, that figures.  We preload the files in lisp/language/, but not
the support some of them need if the corresponding
language-environment is activated.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.