From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Aymeric Agon-Rambosson Newsgroups: gmane.emacs.devel Subject: Re: Finalizing 'inhibit-automatic-native-compilation' Date: Wed, 15 Feb 2023 23:39:19 +0100 Message-ID: <877cwiblk8.fsf@X570GP> References: <837cx8cey0.fsf@gnu.org> <83v8kkxzzx.fsf@gnu.org> <87r0v811pm.fsf@melete.silentflame.com> <87cz6nxdqy.fsf@X570GP> <83357irhnv.fsf@gnu.org> <87ttzy2lgi.fsf@X570GP> <83a61pprm8.fsf@gnu.org> <87mt5ncjuk.fsf@X570GP> <83cz6jm9mo.fsf@gnu.org> <87a61lkjb7.fsf@X570GP> <87pmahs9um.fsf@EBx360> <877cwoo6ru.fsf@X570GP> <83bkm0jxbr.fsf@gnu.org> <87ttzq25m6.fsf@X570GP> <837cwmhlgs.fsf@gnu.org> <87pmae1wrs.fsf@X570GP> <83v8k6fxy5.fsf@gnu.org> <87y1p01qlc.fsf@EBx360> <83y1p0cq3v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32162"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.6.10; emacs 28.1 Cc: akrl@sdf.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca, emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Feb 16 07:58:52 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pSYED-000840-LQ for ged-emacs-devel@m.gmane-mx.org; Thu, 16 Feb 2023 07:58:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pSYDi-0008UV-Ad; Thu, 16 Feb 2023 01:58:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSQR4-0000DF-1U for emacs-devel@gnu.org; Wed, 15 Feb 2023 17:39:34 -0500 Original-Received: from forward500b.mail.yandex.net ([2a02:6b8:c02:900:1:45:d181:d500]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSQR0-0007DN-2T; Wed, 15 Feb 2023 17:39:33 -0500 Original-Received: from iva1-adaa4d2a0364.qloud-c.yandex.net (iva1-adaa4d2a0364.qloud-c.yandex.net [IPv6:2a02:6b8:c0c:a0e:0:640:adaa:4d2a]) by forward500b.mail.yandex.net (Yandex) with ESMTP id 632195F4A4; Thu, 16 Feb 2023 01:39:23 +0300 (MSK) Original-Received: by iva1-adaa4d2a0364.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id KdtnkL4YVeA1-c3VDwcf4; Thu, 16 Feb 2023 01:39:22 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1676500762; bh=kddKq6Gu+QixSHGAy10PqCoXcBZhBgQzaR7YNfh3dMg=; h=Cc:Message-ID:References:Date:Subject:In-reply-to:To:From; b=q/ctQ1oiqa793QWG3RUsJlSzOkhX4FwIY/zjVy6XKAxLinuCWatRLFpfz3k3DpvOV /DkDifbjQ1grIxlAks3/SIt0NoI4zWUhytvggIGsIqZp8sCgYOACstcYI0ewb7vsvt APOI86ZvtZDx1P9Fxi7tavWMHEXAhBDT6LEGLpFc= Authentication-Results: iva1-adaa4d2a0364.qloud-c.yandex.net; dkim=pass header.i=@yandex.com In-reply-to: <83y1p0cq3v.fsf@gnu.org> Received-SPF: pass client-ip=2a02:6b8:c02:900:1:45:d181:d500; envelope-from=aymeric.agon@yandex.com; helo=forward500b.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Thu, 16 Feb 2023 01:58:13 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303363 Archived-At: Le mardi 14 f=C3=A9vrier 2023 =C3=A0 15:51, Eli Zaretskii a= =20 =C3=A9crit : > When will this be useful, and why the existing features don't=20 > already > support whatever use case you had in mind? The use case we want to have supported is for instance when there=20 is no writable home directory, like in the bug report Sean posted=20 in the other branch of this conversation. > As people here pointed out just recently, if Emacs cannot write=20 > a .eln > file, it will still work correctly by using the corresponding=20 > .elc > file. I could be wrong, but it does not seem to be the case for=20 trampolines. In the current state of master, if no writable=20 directory can be found for the output of the .eln file containing=20 the trampoline, emacs errors out. > So why do we need a subtle feature of depositing *.eln files in > a temporary directory The temporary directory ("/tmp/" on POSIX systems) can potentially=20 be the only user-writable directory. So being able to write there=20 as a last resort can guarantee that a trampoline compilation will=20 not produce an error. > (which on many systems is ephemeral, or is > regularly purged)? (In the case of POSIX systems at least, a program can still expect=20 the content of /tmp to be preserved for the duration of its=20 current invocation, according to=20 https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s18.html). I=20 admit I do not know the semantics of the equivalent for Windows. > By the very nature of temporary files and directories created by > Emacs, you cannot know their exact name, and so putting a file=20 > there > would be almost completely useless. So I'm asking when will=20 > this be > useful. I'd like to avoid adding features whose usability is=20 > not well > understood and whose justification is not solid enough. We have=20 > too > many subtle knobs in native-compilation already. The commit added by Andrea (ce4a066ed1e) on the=20 inhibit-native-comp-cleanup branch implements the following=20 behaviour : if no writable directory is found in either=20 `native-comp-target-directory' or in the output of=20 `comp-eln-load-path-eff', a filename in the directory=20 `temporary-file-directory' is returned. This file is guaranteed to=20 be creatable, which is what we wanted to ensure, and we know its=20 exact name (you had a good point there). This is I guess=20 equivalent to what I wanted to ensure with 'compile-but-no-output,=20 so personnally I'm good. But what actually matters are the results=20 of Sean's tests, of course.