Re: Building a release tarball generates trampoline files in eln-cache

[Andrea Corallo]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
>> Date: Thu, 11 Nov 2021 21:01:37 +0000
>> 
>> > Would the code to implement this be complicated?  If not, please show
>> > the code you had in mind, so I could make sure we are on the same
>> > page.
>> 
>> I'm attaching the following patch.  It is very much untested but should
>> clarify what I had in mind.
>
> Thanks.  I think we should do this on master, but on the release
> branch compile gv.el AOT, as that will be safer.  WDYT?

I think is sensible.  I'll prepare and test this for master then.

>> > And while I have your attention, another question: suppose that Emacs
>> > with all the preloaded files compiled to *.eln is installed on a
>> > system that has libgccjit (which AFAIU is necessary to run the
>> > native-compiled code), but doesn't have Binutils -- what will happen
>> > when Emacs loads some .el file and tries to compile it?  Will the
>> > response to the compilation failure be graceful?  (This situation is
>> > likely to happen when users install a binary distro, but don't have
>> > Binutils available.)
>> 
>> I believe binutils is a dependecy of libgccjit, so I guess having
>> libgccjit without binutils should be classified as missconfiguration no?
>
> Dependency in what way?  maybe if one installs from a Linux distro,
> Binutils will be installed as a dependency.

Yes this was the scenarion I was thinking of.

> But if someone downloads
> a precompiled libgccjit DLL on Windows, for example, they will not
> have Binutils unless they also install it.  Because libgccjit is part
> of GCC, and one can AFAIK install MinGW GCC without installing
> Binutils.

Interesting, I didn't know it was a realistic scenarion.

Anyway this was never tested by me but... what should happen is that we
signal and error in `comp--compile-ctxt-to-file'.  For async compilation
this should be eventually reported in the async log buffer.

Best Regards

  Andrea