From: Daniel Colascione <dancol@dancol.org>
To: 10398@debbugs.gnu.org
Subject: bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days
Date: Thu, 29 Dec 2011 06:06:05 -0800 [thread overview]
Message-ID: <31890c3c686da18017fafebac19a6529ee09950d.1325166842.git.dancol@dancol.org> (raw)
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
next reply other threads:[~2011-12-29 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:06 Daniel Colascione [this message]
2012-04-10 23:26 ` bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days 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
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=31890c3c686da18017fafebac19a6529ee09950d.1325166842.git.dancol@dancol.org \
--to=dancol@dancol.org \
--cc=10398@debbugs.gnu.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.