unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>, Ken Brown <kbrown@cornell.edu>
Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: disable automatic native-compilation?
Date: Sun, 10 Jul 2022 18:39:12 +0300	[thread overview]
Message-ID: <838rp10yfz.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bDE+ZrysAvcOJpST+5YJBtme0OU7ch9R0tGESNFSb1uww@mail.gmail.com> (message from Lynn Winebarger on Sun, 10 Jul 2022 11:10:27 -0400)

> 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	other threads:[~2022-07-10 15:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 16:49 disable automatic native-compilation? Stephen Leake
2022-07-09 17:23 ` Eli Zaretskii
2022-07-10 15:10   ` Lynn Winebarger
2022-07-10 15:39     ` Eli Zaretskii [this message]
2022-07-10 18:32       ` Lynn Winebarger
2022-07-10 21:54         ` Ken Brown
2022-07-11  1:52           ` Ken Brown
2022-07-11  2:39             ` Lynn Winebarger
2022-07-11 13:37               ` Ken Brown
2022-07-11 13:56                 ` Eli Zaretskii
2022-07-11 17:19                   ` Ken Brown
2022-07-09 22:36 ` Tor Kringeland
2022-07-10  8:58   ` Philip Kaludercic
2022-07-11 12:54   ` Andrea Corallo
2022-07-12 11:04     ` Tor Kringeland
2022-07-12 11:27       ` Tor Kringeland
2022-07-12 13:29         ` Eli Zaretskii
2022-08-06 15:32 ` Lynn Winebarger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838rp10yfz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kbrown@cornell.edu \
    --cc=owinebar@gmail.com \
    --cc=stephen_leake@stephe-leake.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).