GNU bug report logs - #62004
30.0.50; comp-run-async-workers failure when default-directory deleted

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: 62004 <at> debbugs.gnu.org, iarchivedmywholelife <at> gmail.com
Subject: bug#62004: 30.0.50; comp-run-async-workers failure when default-directory deleted
Date: Tue, 07 Mar 2023 15:17:13 +0200

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: No Wayman <iarchivedmywholelife <at> gmail.com>,  62004 <at> debbugs.gnu.org
> Date: Tue, 07 Mar 2023 11:16:40 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Andrea, any ideas?  How come we never ran into this issue until now?
> 
> I guess it's a very unlikely condition that was never
> encountered/reported.
> 
> > Is the default-directory value when native compilation is forked
> > somehow derived from the directory of the file being compiled?
> 
> If it is is not evident to me why.  We spawan something of this kind
> 
> /pathtoemacs/emacs -Q -batch -l /tmp/emacs-async-comp-something.el
> 
> where emacs-async-comp-something.el contains the actual setup (where we
> don't touch default-directory) and compilation command.
> 
> I'm probably missing something ATM.

Well, maybe we should bind the variable to be on the safe side?  What
if we bind it to the directory where we write that
emacs-async-comp-something.el file?

Previous Next

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