?RCS:
?RCS: Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
?RCS:
-?RCS: You may redistribute only under the terms of the Artistic Licence,
+?RCS: You may redistribute only under the terms of the Artistic License,
?RCS: as specified in the README file that comes with the distribution.
?RCS: You may reuse parts of this distribution only within the terms of
-?RCS: that same Artistic Licence; a copy of which may be found at the root
+?RCS: that same Artistic License; a copy of which may be found at the root
?RCS: of the source tree for dist 4.0.
?RCS:
?RCS: $Log: Head.U,v $
?MAKE:Head:
?MAKE: -pick wipe $@ %<
?V:PATH p_ _exe me newsh
-?T:argv Id p paths OS2_SHELL DJGPP
+?T:argv p paths OS2_SHELL DJGPP
?T:inksh needksh avoidksh newsh changesh reason
?F:!*
?LINT:extern ENV CDPATH SHELL MACHTYPE _exe is_os2
# Note: this Configure script was generated automatically. Rather than
# working with this copy of Configure, you may wish to get metaconfig.
# The dist package (which contains metaconfig) is available via SVN:
-# svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist
+# svn co https://svn.code.sf.net/p/dist/code/trunk/dist
#
?X: OK, I'll not alter, but I'll add to it then ...
# Though this script was generated by metaconfig from metaunits, it is
# OK to send patches against Configure itself. It's up to the Configure
# pumpkin to backport the patch to the metaunits if it is accepted.
+# For more information on patching Configure, see pod/perlhack.pod
+#
# The metaunits are also available from the public git repository:
# http://perl5.git.perl.org/metaconfig.git/ or
# $ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
?X: by your version, not mine: It credits your work.
?X:
-# $Id: Head.U 6 2006-08-25 22:21:46Z rmanfredi $
-#
# Generated on <DATE> [metaconfig <VERSION> PL<PATCHLEVEL>]
# (with additional metaconfig patches by <MAINTLOC>)
rm -f c1$$ c2$$
if test -f /dev/cputype -a -f /dev/drivers -a -f /dev/osversion; then
- cat >&4 <<EOF
+ cat <<EOF
***
*** I'm sorry but this system looks like Plan 9 and Plan 9 doesn't do
*** Configure that well. (Plan 9 is close to UNIX but not close enough.)
fi
if test ! -c /dev/null ; then
- cat >&4 <<EOF
+ cat <<EOF
***
*** I'm sorry, but /dev/null appears to be a file rather than a device.
*** Please consult your operating sytem's notes for making a device
?X:
?X: To be able to run under OS/2, we must detect that early enough to use
?X: the proper path separator, stored in $p_. It is : on UNIX and ; on
-?X: DOSish systems such as OS/2.
+?X: DOS-ish systems such as OS/2.
?X:
: Proper separator for the PATH environment variable
p_=:
: On OS/2 this directory should exist if this is not floppy only system ":-]"
-if test -d c:/. || ( uname -a | grep -i 'os\(/\|\)2' ) 2>&1 >/dev/null ; then
+if test -d c:/. || ( uname -a | grep -i 'os\(/\|\)2' 2>&1 ) 2>&1 >/dev/null ; then
if test -n "$OS2_SHELL"; then
p_=\;
PATH=`cmd /c "echo %PATH%" | tr '\\\\' / `
is_os2=yes
elif test -n "$DJGPP"; then
case "X${MACHTYPE:-nonesuchmach}" in
- *cygwin) ;;
+ *cygwin|*msys) ;;
*) p_=\; ;;
esac
fi
?X: There are two schools of thoughts here. Some people correctly argue that
?X: the user has a better chance than we do of setting a reasonable PATH and
?X: others argue that Configure is the best place there is to set up a suitable
-?X: PATH. Well, here we try to compromize by keeping the user's PATH and
+?X: PATH. Well, here we try to compromise by keeping the user's PATH and
?X: appending some directories which are known to work on some machine or the
?X: other. The rationale behind this being that a novice user might not have a
?X: proper environment variable set, and some directories like /etc (where
;;
esac
?X: Warn them if they use ksh on other systems, which are those where
-?X: we don't need ksh nor want to avoid it explicitely, yet are using it.
+?X: we don't need ksh nor want to avoid it explicitly, yet are using it.
case "$inksh/$needksh-$avoidksh-" in
true/--)
cat <<EOM
?X: 2004.06.09 rac
?X: having $newsh persist as ksh here is bad news if ksh doesn't really
?X: exist. this causes us to toss away a perfectly good working test in
-?X: bash in favour of more exotic external options. see bug 42665.
+?X: bash in favor of more exotic external options. see bug 42665.
test -x "${newsh}" || unset newsh
?X: Unset CDPATH to avoid surprises when using cd under some shells