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

[Andrea Corallo <akrl@sdf.org>]

Sean Whitton <spwhitton@spwhitton.name> writes:

> Hello,
>
> On Sat 11 Feb 2023 at 11:16AM +02, Eli Zaretskii wrote:
>
>> The bug report you posted, https://bugs.debian.org/1021842, is not a
>> crash, it is a failure which happens when a 3rd-party package is used.
>> I see no detailed analysis of the error in the bug report, so I can
>> only speculate what could be the reasons for the error:
>>
>>   . buttercup was not updated to work with native-compilation (was
>>     this failure reported to the buttercup developers?)
>>   . Debian test harness uses buttercup incorrectly when
>>     native-compilation is enabled (e.g., it doesn't set up
>>     native-comp-eln-load-path to allow the trampolines to be produced)
>>   . the test that failed should only be run if Emacs was built without
>>     native-compilation
>
> I posted that particular bug because it's one that occurs precisely when
> HOME is not writeable, and not otherwise, and the error output says that
> the problem is not being able to write to HOME.  But it sounds like you
> think someone who enables native comp is also responsible for setting up
> trampoline redirection in the event that HOME is not writeable; i.e.,
> the idea that Emacs should be able to do everything not explicitly
> involving HOME without a writeable HOME doesn't hold once native-comp is
> enabled.

Hi Sean,

this should be fixed by the last commit in
feature/inhibit-native-comp-cleanup (ce4a066ed1e).

Please let us know if this solution works for you.

Thanks

  Andrea