[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Finalizing 'inhibit-automatic-native-compilation'

From: Eli Zaretskii
Subject: Re: Finalizing 'inhibit-automatic-native-compilation'
Date: Thu, 16 Feb 2023 10:04:46 +0200

> From: Aymeric Agon-Rambosson <aymeric.agon@yandex.com>
> Cc: akrl@sdf.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca,
>  emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org
> Date: Wed, 15 Feb 2023 23:39:19 +0100
> Le mardi 14 février 2023 à 15:51, Eli Zaretskii <eliz@gnu.org> a 
> écrit :
> > When will this be useful, and why the existing features don't 
> > already
> > support whatever use case you had in mind?
> The use case we want to have supported is for instance when there 
> is no writable home directory, like in the bug report Sean posted 
> in the other branch of this conversation.

That use case should be solved now by recent Andrea's work.

> The commit added by Andrea (ce4a066ed1e) on the 
> inhibit-native-comp-cleanup branch implements the following 
> behaviour : if no writable directory is found in either 
> `native-comp-target-directory' or in the output of 
> `comp-eln-load-path-eff', a filename in the directory 
> `temporary-file-directory' is returned. This file is guaranteed to 
> be creatable, which is what we wanted to ensure, and we know its 
> exact name (you had a good point there). This is I guess 
> equivalent to what I wanted to ensure with 'compile-but-no-output, 
> so personnally I'm good. But what actually matters are the results 
> of Sean's tests, of course.

OK, so let's consider this issue resolved, until and unless Sean
reports some problems with the solution.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]