Re: Suppressing native compilation (short and long term)

[Lars Ingebrigtsen]

Andrea Corallo <akrl@sdf.org> writes:

>>>> I think it's a fine solution, but either comp-spawned-compilation
>>>> should be renamed to comp-no-spawn, or its value in the forked Emacs
>>>> processes should be nil...

[...]

> Okay 1a8015b837 should do the job.  I eventually opted for adding
> `comp-no-spawn' for now, seen the current "debated" situation on what we
> should offer as interface to the user, I thought was better for now to
> add a variable supposed to be used for internal use only.  We can remove
> it and link the mechanism to `native-comp-async-jobs-number' afterwards
> if we decide for it.

Is this supposed to fix the trampoline fork bomb?  (There's a lot of
stuff discussed in this thread...)  If so, it doesn't, because the
variable is set too late.  (As Eli suggested in another thread, we
should add a command line argument for this, and as I noted, that kind
of fits with the stuff discussed in bug#58509.)