From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 62004@debbugs.gnu.org, iarchivedmywholelife@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 [thread overview]
Message-ID: <831qm07lba.fsf@gnu.org> (raw)
In-Reply-To: <xjfo7p4vmjr.fsf@ma.sdf.org> (message from Andrea Corallo on Tue, 07 Mar 2023 11:16:40 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: No Wayman <iarchivedmywholelife@gmail.com>, 62004@debbugs.gnu.org
> Date: Tue, 07 Mar 2023 11:16:40 +0000
>
> Eli Zaretskii <eliz@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?
next prev parent reply other threads:[~2023-03-07 13:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:48 bug#62004: 30.0.50; comp-run-async-workers failure when default-directory deleted No Wayman
2023-03-06 16:49 ` Eli Zaretskii
2023-03-06 17:20 ` No Wayman
2023-03-06 18:31 ` Eli Zaretskii
2023-03-06 18:46 ` No Wayman
2023-03-06 20:10 ` Eli Zaretskii
2023-03-06 21:29 ` No Wayman
2023-03-07 3:30 ` Eli Zaretskii
[not found] ` <xjfo7p4vmjr.fsf@ma.sdf.org>
2023-03-07 13:17 ` Eli Zaretskii [this message]
2023-03-07 13:51 ` Andrea Corallo
2023-03-07 14:16 ` Eli Zaretskii
2023-03-07 15:20 ` No Wayman
2023-03-07 15:53 ` No Wayman
2023-03-07 16:06 ` Andrea Corallo
2023-03-07 16:14 ` Eli Zaretskii
2023-03-07 16:30 ` No Wayman
2023-03-08 20:19 ` Andrea Corallo
2023-03-08 20:51 ` No Wayman
2023-03-09 9:25 ` Andrea Corallo
2023-03-07 16:00 ` 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=831qm07lba.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62004@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=iarchivedmywholelife@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).