From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10398@debbugs.gnu.org, larsi@gnus.org
Subject: bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days
Date: Wed, 11 Apr 2012 22:51:45 -0400 [thread overview]
Message-ID: <4F864341.807@cornell.edu> (raw)
In-Reply-To: <83zkai3w8t.fsf@gnu.org>
On 4/11/2012 3:26 PM, Eli Zaretskii wrote:
> I think we should put our money where our mouth is. If we consider
> Cygwin 1.5 unsupported, we should at least warn the prospective users
> that they are building Emacs with unsupported tools.
>
> So yes, I think we should insert a warning now. Could you please make
> such a change? TIA.
How's this:
=== modified file 'configure.in'
--- configure.in 2012-04-02 04:38:31 +0000
+++ configure.in 2012-04-12 02:38:52 +0000
@@ -3805,6 +3805,14 @@
echo
fi
+if test "${opsys}" = "cygwin"; then
+ cygwin_rel=`uname -r|sed -e 's/\(^1\.[[579]]\)\..*/\1/'`
+ if test "${cygwin_rel}" = "1.5"; then
+ echo
+ echo "*** Warning: Building Emacs on Cygwin 1.5 is not supported."
+ echo
+ fi
+fi
# Remove any trailing slashes in these variables.
[test "${prefix}" != NONE &&
FYI, here's what the output of `uname -r' looks like on Cygwin:
$ uname -r
1.7.14s(0.260/5/3)
next prev parent reply other threads:[~2012-04-12 2:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:06 bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days Daniel Colascione
2012-04-10 23:26 ` Lars Magne Ingebrigtsen
2012-04-11 6:47 ` Chong Yidong
2012-04-11 6:58 ` Eli Zaretskii
2012-04-11 11:15 ` Ken Brown
2012-04-11 11:39 ` Eli Zaretskii
2012-04-11 12:35 ` Ken Brown
2012-04-11 19:26 ` Eli Zaretskii
2012-04-12 2:51 ` Ken Brown [this message]
2012-04-12 4:53 ` Glenn Morris
2012-04-12 6:00 ` Eli Zaretskii
2012-04-12 7:40 ` Andreas Schwab
2012-04-12 12:21 ` Ken Brown
2012-04-11 17:48 ` Drew Adams
2012-04-11 19:37 ` Ken Brown
2012-04-11 20:04 ` Drew Adams
2012-04-11 11:44 ` Lars Magne Ingebrigtsen
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=4F864341.807@cornell.edu \
--to=kbrown@cornell.edu \
--cc=10398@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.