Re: Deferring native compilation finalization until idle
"Aaron Jensen" <[email protected]> Sat, 25 Jul 2026 18:01:26 +0000
| Newsgroups | gmane.emacs.devel |
|---|---|
| Message-ID | <ms0ocoeu.4faab67d-20a5-4283-b441-66e776be7c35@we.are.superhuman.com> |
On Sat, Jul 25, 2026 at 10:38 AM, Lynn Winebarger < [email protected] > wrote: > > On Sat, Jul 25, 2026, 12:23 PM Aaron Jensen < aaronjensen@ gmail. com ( > [email protected] ) > wrote: > > >> >> >> No, this is not what the problem is. That's the thing that I'm saying has >> been pretty well established in this thread, though it seems not well >> enough. >> >> >> >> The problem is that macOS, upon first *loading* the bundle in the main >> Emacs process will undergo a security check (the one disabled by the >> entitlements call you posted). This is a synchronous, blocking operation. >> MacOS does not allow the process to load the bundle until it has verified >> it, so the load is blocking. >> >> > > > > Just out of curiosity, could this be approached by treating the > verification step as part of the compilation? Could the library be > verified while loaded from some non-standard location (in an asynchronous > instance of Emacs) then moved to the ordinary eln cache directory? Or, if > it must be verified in place, only load verified libraries implicitly > (launching asynchronous instances to do the verification load as > necessary)? > > > > Lynn > > This is what is detailed in PROBLEMS, effectively adding validation/first load to the async worker compilation step. Aaron > > >> >>> >>>> >>>> >>>> >>> >>> >> >> >> >> > >