[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finalizing 'inhibit-automatic-native-compilation'
From: |
Andrea Corallo |
Subject: |
Re: Finalizing 'inhibit-automatic-native-compilation' |
Date: |
Tue, 14 Feb 2023 11:29:04 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
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
- Re: Finalizing 'inhibit-automatic-native-compilation', (continued)
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/09
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/10
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/10
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/11
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/13
- Re: Finalizing 'inhibit-automatic-native-compilation', tomas, 2023/02/14
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/14
- Re: Finalizing 'inhibit-automatic-native-compilation',
Andrea Corallo <=
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/14
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/16
- Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/17
- Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/17
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/17
- Re: Finalizing 'inhibit-automatic-native-compilation', Tatsuya Kinoshita, 2023/02/18
- Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/18
- Re: Finalizing 'inhibit-automatic-native-compilation', Stefan Monnier, 2023/02/18
- Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/20
- Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/20