[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: disable automatic native-compilation?

From: Lynn Winebarger
Subject: Re: disable automatic native-compilation?
Date: Sun, 10 Jul 2022 14:32:54 -0400

I see a discussion under bug #50666 -
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50666 [ note - only
found by google site search on lists.gnu.org for "Ken Brown" "cygwin"
"native", the bug did not show up when I used debbugs's search for
bugs for package "emacs" with "cygwin" in the subject ].
It seems to have focused on the 32-bit architecture, but I only use
64-bit targets.
I'm updating dozens of packages at a time, although the practical
limit seems to be 20-30 in a pass before I get an error about having
run out of some resource (process ids or file descriptors or something
along those lines, not sure).  In any case, if the eln files are
asynchronously getting rebased before being loaded, perhaps there's a
race condition somewhere?
I can file a bug if merited.


On Sun, Jul 10, 2022 at 11:39 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Lynn Winebarger <owinebar@gmail.com>
> > Date: Sun, 10 Jul 2022 11:10:27 -0400
> > Cc: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel 
> > <emacs-devel@gnu.org>
> >
> > If Stephen's building native compilation under cygwin, perhaps he's
> > referring to an error message about not being able to load the ELN
> > file, either in the form of a "fork" failure, or an explicit complaint
> > about the dll base address conflicting with another dll that's already
> > been loaded.  For a 64-bit build, a restart of emacs seems to be
> > enough to cure the issue, although I have also had issues that didn't
> > seem to be resolved without doing a "rebase all".
> > I don't know if this behavior is considered a bug (in either libgccjit
> > or emacs) or just a basic limitation of using the cygwin platform.
> > It is definitely an annoyance when either installing packages or when
> > one of the package's features/modules is autoloaded the first time.
> This was discussed with Ken Brown (CC'ed) at some point, but I don't
> remember what was the conclusion for the future.
> (And I don't think Stephen uses Cygwin.  But I may be mistaken.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]