* unix/configure.in:

	* unix/tcl.m4:
	* unix/tclUnixPipe.c: removed checking for compatible vfork
	function and use of the vfork function.  Modern VM systems rarely
	suffer any performance degradation when fork is used, and it
	solves multiple problems with vfork.  Users that still want vfork
	and add -Dfork=vfork to the compile flags. [Bug: 942 2228 1312]

1 files changed, 1 insertions, 11 deletions

diff --git a/unix/configure.in b/unix/configure.in
index 316b9f8..430e944 100644
--- a/unix/configure.in
+++ b/unix/configure.in
@@ -2,7 +2,7 @@ dnl	This file is an input file used by the GNU "autoconf" program to
 dnl	generate the file "configure", which is run during Tcl installation
 dnl	to configure the system for the local environment.
 AC_INIT(../generic/tcl.h)
-# RCS: @(#) $Id: configure.in,v 1.50 1999/10/05 22:46:40 hobbs Exp $
+# RCS: @(#) $Id: configure.in,v 1.51 1999/12/12 02:27:19 hobbs Exp $
 
 TCL_VERSION=8.3
 TCL_MAJOR_VERSION=8
@@ -334,16 +334,6 @@ if test $tcl_ok = yes; then
 fi
 
 #--------------------------------------------------------------------
-# Check to see whether the system provides a vfork kernel call.
-# If not, then use fork instead.  Also, check for a problem with
-# vforks and signals that can cause core dumps if a vforked child
-# resets a signal handler.  If the problem exists, then use fork
-# instead of vfork.
-#--------------------------------------------------------------------
-
-SC_HAVE_VFORK
-
-#--------------------------------------------------------------------
 #	Check whether there is an strncasecmp function on this system.
 #	This is a bit tricky because under SCO it's in -lsocket and
 #	under Sequent Dynix it's in -linet.