--- Begin Message ---
Subject: |
[PATCH] Use real vfork under Cygwin: it's fine these days |
Date: |
Thu, 29 Dec 2011 06:06:05 -0800 |
In Cygwin 1.7, vfork is an alias for fork. The vfork the #define in
cygwin.h was protecting against is gone. It's better to use vfork now
so that when Cygwin gains a new, working vfork, we use it
automatically.
---
src/s/cygwin.h | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/src/s/cygwin.h b/src/s/cygwin.h
index 8f5a0ab..e025e46 100644
--- a/src/s/cygwin.h
+++ b/src/s/cygwin.h
@@ -81,10 +81,6 @@ along with GNU Emacs. If not, see
<http://www.gnu.org/licenses/>. */
#define HAVE_SOCKETS
-/* vfork() interacts badly with setsid(), causing ptys to fail to
- change their controlling terminal */
-#define vfork fork
-
/* This should work (at least when compiling with gcc). But I have no way
or intention to verify or even test it. If you encounter a problem with
it, feel free to change this setting, but please add a comment here about
--
1.7.5.1
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days |
Date: |
Thu, 12 Apr 2012 08:21:31 -0400 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 |
On 4/12/2012 3:40 AM, Andreas Schwab wrote:
Ken Brown<address@hidden> writes:
+if test "${opsys}" = "cygwin"; then
+ cygwin_rel=`uname -r|sed -e 's/\(^1\.[[579]]\)\..*/\1/'`
Why do you need the filter?
case `uname -r` in 1.5.*) ...
Thanks. And thanks to Glenn for telling me about AC_MSG_WARN. I've
committed the change to the trunk (bzr revision 107877), and I'm closing
the bug.
Ken
--- End Message ---