From: Ken Brown <kbrown@cornell.edu>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stephen Leake <stephen_leake@stephe-leake.org>,
emacs-devel <emacs-devel@gnu.org>,
Achim Gratz <Stromeko@nexgo.de>
Subject: Re: disable automatic native-compilation?
Date: Mon, 11 Jul 2022 09:37:35 -0400 [thread overview]
Message-ID: <a011a1d3-51fc-9d7a-d8ea-3d1f205694c1@cornell.edu> (raw)
In-Reply-To: <CAM=F=bAVKv7iPdNWO+ADYd8a6KM6iTp_c7R+Jgz9t0Qq0JhRNw@mail.gmail.com>
On 7/10/2022 10:39 PM, Lynn Winebarger wrote:
> On Sun, Jul 10, 2022, 9:53 PM Ken Brown <kbrown@cornell.edu
> <mailto:kbrown@cornell.edu>> wrote:
>
> On 7/10/2022 5:54 PM, Ken Brown wrote:
> > Native compilation is unusable on 32-bit Cygwin, and this is reflected in
> the
> > configure script. (See the --with-cygwin32-native-compilation configure
> option.)
> >
> > In the 64-bit case, Achim Gratz's autorebase postinstall script takes
> care of
> > rebasing the .eln files on a regular basis, provided the user has set
> things up
> > appropriately. Instructions can be found in the announcement at
> >
> > https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html
> <https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html>
> >
> > In the 3 months since I sent that announcement, I have not heard from a
> single
> > Cygwin user about rebase issues. This might simply mean that very few users
> > have tried the native compilation release.
>
>
> Will do, but could you include the details of the announcement in the emacs
> source distribution somewhere, as is done for the other variants with specific
> instructions? I'm only incidentally building it in a cygwin environment - it
> didn't even occur to me to check the general cygwin mailing list.
Yes, I'll add something to etc/PROBLEMS unless you or Eli can suggest a better
place.
> >
> > I myself use that release daily, and I can only recall one instance in
> which I
> > saw a fork failure and had to exit emacs and rebase.
> >
> > In summary, I would say that native compilation is usable with very
> occasional
> > minor annoyances on 64-bit Cygwin. But I doubt if I will ever make it the
> > default Cygwin build, simply because I don't want to be inundated with
> emails
> > from people who haven't read the release announcement.
>
> Lynn,
>
> Rereading your earlier message about problems during package installation, I
> see
> I didn't really respond to that. But it has nothing to do with the present
> bug,
> so please make a fresh bug report and give full details. And please follow the
> instructions in the announcement I cited. If you're working in your own build
> of Cygwin emacs that you haven't installed, you might also have to add its
> native-lisp directory to
>
> /var/lib/rebase/userpath.d/<username>
>
>
> I am doing exactly what you surmised, running a build I haven't installed - in
> fact that I built with --prefix=/does/not/exist/ to ensure system installed
> site-lisp files will not get injected into the load-path while doing do. So
> I'll try that first. Although I think the packages generating the fork failures
> should be going into the cache in my home directory.
That's true, but Cygwin's autorebase facility needs to know about *all* .eln
files that might be used, in order to try to maintain a conflict-free set of
base addresses.
And I forgot to say that after you've created
/var/lib/rebase/userpath.d/<username> with the appropriate paths, you should
shut down all Cygwin processes and run Cygwin's setup program. (You don't have
to install anything; this is just to let the autorebase postinstall script run.)
> If there are still issues, did you mean to log a bug with cygwin or emacs?
I meant emacs. Thanks.
Ken
next prev parent reply other threads:[~2022-07-11 13:37 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
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 [this message]
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=a011a1d3-51fc-9d7a-d8ea-3d1f205694c1@cornell.edu \
--to=kbrown@cornell.edu \
--cc=Stromeko@nexgo.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).