nuke some dead code
This commit is contained in:
parent
b99edc6cc1
commit
429f327c0a
8
Makefile
8
Makefile
@ -1,4 +1,4 @@
|
|||||||
# $MirBSD: src/bin/ksh/Makefile,v 2.1 2004/12/10 18:09:40 tg Exp $
|
# $MirBSD: src/bin/ksh/Makefile,v 2.2 2004/12/13 16:50:50 tg Exp $
|
||||||
# $OpenBSD: Makefile,v 1.18 2004/02/16 19:07:19 deraadt Exp $
|
# $OpenBSD: Makefile,v 1.18 2004/02/16 19:07:19 deraadt Exp $
|
||||||
|
|
||||||
PROG= ksh
|
PROG= ksh
|
||||||
@ -26,8 +26,8 @@ siglist.out: config.h sh.h siglist.in siglist.sh
|
|||||||
emacs.out: emacs.c
|
emacs.out: emacs.c
|
||||||
${SHELL} ${.CURDIR}/emacs-gen.sh ${.CURDIR}/emacs.c >emacs.out
|
${SHELL} ${.CURDIR}/emacs-gen.sh ${.CURDIR}/emacs.c >emacs.out
|
||||||
|
|
||||||
check test:
|
check:
|
||||||
${SHELL} ${.CURDIR}/tests/th.sh ${.CURDIR}/tests/th \
|
/usr/bin/perl ${.CURDIR}/tests/th -s ${.CURDIR}/tests \
|
||||||
-s ${.CURDIR}/tests -p ./ksh -C pdksh,sh,ksh,posix,posix-upu
|
-p ./ksh -C pdksh,sh,ksh,posix,posix-upu
|
||||||
|
|
||||||
.include <bsd.prog.mk>
|
.include <bsd.prog.mk>
|
||||||
|
22
tests/README
22
tests/README
@ -1,22 +0,0 @@
|
|||||||
Tests can be assigned categories to restrict what program they
|
|
||||||
are applied to (eg, pdksh, ksh88, etc.). The following are
|
|
||||||
a list of names to be used for various shells (to keep things
|
|
||||||
consistent):
|
|
||||||
|
|
||||||
sh generic any v7 bourne shell like thing
|
|
||||||
sh-v generic any system V bourne shell like thing
|
|
||||||
ksh generic any ksh
|
|
||||||
posix generic basic posix shell
|
|
||||||
posix-upu generic 'user portability utility' options
|
|
||||||
sh-v7 specific the real v7 bourne shell
|
|
||||||
sh-sysv specific the real sysv bourne shell
|
|
||||||
pdksh specific public domain ksh
|
|
||||||
ksh88 specific at&t ksh88
|
|
||||||
ksh93 specific at&t ksh93
|
|
||||||
bash specific GNU bourne-again shell
|
|
||||||
|
|
||||||
The idea is to categorize all the tests according to the 'best match'
|
|
||||||
(most generic thing). All generics that apply should be specified.
|
|
||||||
Generally, at most one specific shell will be given.
|
|
||||||
|
|
||||||
At the moment, most (all) tests have not been categorized (any volunteers?).
|
|
29
tests/th.sh
29
tests/th.sh
@ -1,29 +0,0 @@
|
|||||||
#!/bin/sh
|
|
||||||
# $MirBSD: src/bin/ksh/tests/th.sh,v 2.1 2004/12/10 18:09:45 tg Exp $
|
|
||||||
# $OpenBSD: th.sh,v 1.4 2001/01/28 23:04:57 niklas Exp $
|
|
||||||
#
|
|
||||||
# Simple script to find perl and run it
|
|
||||||
#
|
|
||||||
|
|
||||||
# Avoid common problems with ENV (though perl shouldn't let it through)
|
|
||||||
# (can you believe some shells don't have an unset???)
|
|
||||||
unset ENV
|
|
||||||
|
|
||||||
x=x
|
|
||||||
[ -x /bin/sh ] 2> /dev/null || x=f
|
|
||||||
|
|
||||||
IFS=:$IFS
|
|
||||||
perl=
|
|
||||||
for i in $PATH; do
|
|
||||||
[ X"$i" = X ] && i=.
|
|
||||||
for j in perl perl4 perl5 ; do
|
|
||||||
[ -$x "$i/$j" ] && perl=$i/$j && break 2
|
|
||||||
done
|
|
||||||
done
|
|
||||||
|
|
||||||
[ X"$perl" = X ] && {
|
|
||||||
echo "$0: can't find perl - bye\n" 1>&2
|
|
||||||
exit 1
|
|
||||||
}
|
|
||||||
|
|
||||||
exec $perl "$@"
|
|
Loading…
x
Reference in New Issue
Block a user