Subject: bug#58429: 29.0.50; inhibit-automatic-native-compilation does not work as expected.

From: Eli Zaretskii <[email-masked]>
Date: Wed, 12 Oct 2022 20:07:08 +0300

> From: Max Brieiev <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked]
> Date: Wed, 12 Oct 2022 19:54:00 +0300
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> >> From: Max Brieiev <[email-masked]>
> >> Cc: [email-masked],  [email-masked],  [email-masked]
> >> Date: Wed, 12 Oct 2022 17:11:14 +0300
> >> 
> >> Eli Zaretskii <[email-masked]> writes:
> >> 
> >> > Where do you see a message saying that the error is about creating the
> >> > file on disk?  The error message you quoted was different:
> >> >
> >> >   x86_64-unknown-linux-gnu-gcc-10.3.0: fatal error: cannot execute ‘as’: execvp: No such file or directory
> >> >
> >> 
> >> But it also says:
> >> 
> >>     Compiling /tmp/comp-lambda-RCGJQI.eln
> >
> > Yes, but that's not an error message, that's an announcement of what
> > Emacs tries to do.
> 
> Right, and the question was whether this was the correct behaviour for
> Emacs to try to produce eln files, when
> inhibit-automatic-native-compilation was non-nil.

Yes, it is.  When you use some Lisp that advises primitives, Emacs
with native-compilation must generate a trampoline, and
inhibit-automatic-native-compilation cannot prevent that.