summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>1999-03-28 08:29:51 +0000
committerGurusamy Sarathy <gsar@cpan.org>1999-03-28 08:29:51 +0000
commitcc1e6883c8fd5d623dd32359ed8bd44da64c588a (patch)
treeb1a84c85ed4e710e576bb1df24ad0e4c2f5b649c
parent2aa9e77ea0e31c859aef7870ed9bcb63e88566c3 (diff)
downloadperl-cc1e6883c8fd5d623dd32359ed8bd44da64c588a.tar.gz
integrate change#3147 from mainline
warn about newfangled vfork() caveats p4raw-link: @3147 on //depot/perl: 454f2888fcb3cc0830fef0020890cac2dabe9d66 p4raw-id: //depot/maint-5.005/perl@3190
-rwxr-xr-xConfigure11
1 files changed, 10 insertions, 1 deletions
diff --git a/Configure b/Configure
index c710f04dac..5bcdbdaa5c 100755
--- a/Configure
+++ b/Configure
@@ -9206,7 +9206,16 @@ $define)
false) dflt='n';;
*) dflt='y';;
esac
- rp="Some systems have problems with vfork(). Do you want to use it?"
+ cat <<'EOM'
+
+Perl can only use a vfork() that doesn't suffer from strict
+restrictions on calling functions or modifying global data in
+the child. For example, glibc-2.1 contains such a vfork()
+that is unsuitable. If your system provides a proper fork()
+call, chances are that you do NOT want perl to use vfork().
+
+EOM
+ rp="Do you still want to use vfork()?"
. ./myread
case "$ans" in
y|Y) ;;