From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Emacs crashing after M-x compile after Cygwin updates
Date: Mon, 4 Apr 2022 22:17:36 +0900 [thread overview]
Message-ID: <20220404221736.9963544ed157f9ccbe437b33@nifty.ne.jp> (raw)
In-Reply-To: <2130709370.2295152.1649077707001@mail.yahoo.com>
On Mon, 4 Apr 2022 13:08:27 +0000 (UTC)
Bruce Mardle wrote:
> Hi, all.
> I've been happily compiling simple C programs under Emacs (emacs-w32) under Cygwin. Yesterday I wanted to install libedit-dev. While I was doing that, setup...exe marked a few dozen other packages for upgrades. I didn't notice which. Now, if I `emacs hello.c` and M-x compile gcc -o hello hello.c the compilation works... but then, a few seconds later, Emacs SEGVs. emacs-nox does the same but without the delay.
> I've tried Emacs versions 27.2-1, 28.0.60-1.f7e6c199bf, and 27.1. Then, in case it was gcc doing something naughty, I changed that from version 11.2.0 to 10.2.0-1. Same problem all the way. Running gcc from the terminal emulator works (but then I don't get to use Emacs' M-x ` and the like).
> I'm using 64-bit Windows 7 Pro [blush]. Is it still supposed to work on that? I don't seem to have a problem with a laptop running Windows 10.
> `uname -r` returns 3.3.4(0.341/5/3).
> I've spent a few hours looking at the mailing list archives (probably incompetently) and Googling, without success.
Perhaps this is the same issue with:
https://cygwin.com/pipermail/cygwin/2022-March/251162.html
which is already fixed in cygwin git head.
https://cygwin.com/pipermail/cygwin-patches/2022q1/011865.html
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-04-04 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2130709370.2295152.1649077707001.ref@mail.yahoo.com>
2022-04-04 13:08 ` Bruce Mardle
2022-04-04 13:17 ` Takashi Yano [this message]
2022-04-04 18:25 ` Achim Gratz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220404221736.9963544ed157f9ccbe437b33@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
/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.
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).