applied suggested patch with whitespace adjustments

[p5sagit/p5-mst-13.2.git] / hints / machten.sh

diff --git a/hints/machten.sh b/hints/machten.sh
index 75cbc0d..cc663a9 100644 (file)
--- a/hints/machten.sh
+++ b/hints/machten.sh
@@ -13,6 +13,15 @@
 #      Martijn Koster <m.koster@webcrawler.com>
 #      Richard Yeh <rcyeh@cco.caltech.edu>
 #
+# Disable shadow password file access: MT 4.1.1 has necessary library
+# functions, but not header file (or documentation)
+#                      -- Dominic Dunlop <domo@computer.org> 990804
+# For now, explicitly disable dynamic loading -- MT 4.1.1 has it,
+# but these hints do not yet support it.
+# Define NOTEDEF_MACHTEN to undo gratuitous Tenon hack to signal.h.
+#                      -- Dominic Dunlop <domo@computer.org> 9800802
+# Completely disable SysV IPC pending more complete support from Tenon
+#                      -- Dominic Dunlop <domo@computer.org> 980712
 # Use vfork and perl's malloc by default
 #                      -- Dominic Dunlop <domo@computer.org> 980630
 # Raise perl's stack size again; cut down reg_infty; document
@@ -30,8 +39,23 @@
 #
 # Comments, questions, and improvements welcome!
 #
-# MachTen 4.X does support dynamic loading, but perl doesn't
+# MachTen 4.1.1's support for shadow password file access is incomplete:
+# disable its use completely.
+d_endspent=${d_endspent:-undef}
+d_getspent=${d_getspent:-undef}
+d_getspnam=${d_getspnam:-undef}
+d_setspent=${d_setspent:-undef}
+
+# MachTen 4.1.1 does support dynamic loading, but perl doesn't
 # know how to use it yet.
+usedl=${usedl:-undef}
+
+# MachTen 4.1.1 may have an unhelpful hack in /usr/include/signal.h.
+# Undo it if so.
+if grep NOTDEF_MACHTEN /usr/include/signal.h > /dev/null
+then
+    ccflags="$ccflags -DNOTDEF_MACHTEN"
+fi
 
 # Power MachTen is a real memory system and its standard malloc
 # has been optimized for this. Using this malloc instead of Perl's
@@ -50,13 +74,6 @@ usemymalloc=${usemymalloc:-y}
 # Do not wrap the following long line
 malloc_cflags='ccflags="$ccflags -DPLAIN_MALLOC -DNO_FANCY_MALLOC -DUSE_PERL_SBRK"'
 
-# Note that an empty malloc_cflags appears in config.sh if perl's
-# malloc() is not used.  his is harmless.
-case "$usemymalloc" in
-n) unset malloc_cflags;;
-*) ccflags="$ccflags  -DHIDEMYMALLOC"
-esac
-
 # When MachTen does a fork(), it immediately copies the whole of
 # the parent process' data space for the child.  This can be
 # expensive.  Using vfork() where appropriate avoids this cost.
@@ -136,8 +153,12 @@ alignbytes=8
 # friends.  Use setjmp and friends instead.
 expr "$osvers" \< "4.0.3" > /dev/null && d_sigsetjmp='undef'
 
-# semctl(.., ..,  IPC_STATUS, ..) hangs system: say we don't have semctl()
-d_semctl='undef'
+# System V IPC support in MachTen 4.1 is incomplete (missing msg function
+# prototypes, no ftok()), buggy (semctl(.., ..,  IPC_STATUS, ..) hangs
+# system), and undocumented.  Claim it's not there until things improve.
+d_msg=${d_msg:-undef}
+d_sem=${d_sem:-undef}
+d_shm=${d_shm:-undef}
 
 # Get rid of some extra libs which it takes Configure a tediously
 # long time never to find on MachTen
@@ -164,11 +185,12 @@ cat <<EOM >&4
 During Configure, you may see the message
 
 *** WHOA THERE!!! ***
-    The recommended value for \$d_semctl on this machine was "undef"!
+    The recommended value for \$d_msg on this machine was "undef"!
     Keep the recommended value? [y]
 
-Select the default answer: semctl() is buggy, and perl should be built
-without it.
+as well as similar messages concerning \$d_sem and \$d_shm.  Select the
+default answers: MachTen 4.1 appears to provide System V IPC support,
+but it is incomplete and buggy: perl should be built without it.
 
 Similarly, when you see
 
@@ -179,6 +201,11 @@ Similarly, when you see
 select the default answer: vfork() works, and avoids expensive data
 copying.
 
+You may also see "WHOA THERE!!!" messages concerning \$d_endspent,
+\$d_getspent, \$d_getspnam and \$d_setspent.  In all cases, select the
+default answer: MachTen's support for shadow password file access is
+incomplete, and should not be used.
+
 At the end of Configure, you will see a harmless message
 
 Hmm...You had some extra variables I don't know about...I'll try to keep 'em.