Re: Problem with test(1)

2007-04-06 Thread Joe Marcus Clarke
On Thu, 2007-04-05 at 10:08 -0500, Dan Nelson wrote: > In the last episode (Apr 05), Joe Marcus Clarke said: > > I noticed something weird with test(1) when I ran across a problem port > > Makefile. Our test(1) doesn't properly check to make sure there is an > > operand argument to unary operators

Re: Problem with test(1)

2007-04-05 Thread Dan Nelson
In the last episode (Apr 05), Joe Marcus Clarke said: > I noticed something weird with test(1) when I ran across a problem port > Makefile. Our test(1) doesn't properly check to make sure there is an > operand argument to unary operators like -f. For example: > > test -f > > Will print "TRUE" o

Problem with test(1)

2007-04-05 Thread Joe Marcus Clarke
I noticed something weird with test(1) when I ran across a problem port Makefile. Our test(1) doesn't properly check to make sure there is an operand argument to unary operators like -f. For example: test -f Will print "TRUE" on FreeBSD. On Solaris, it will die: /usr/bin/test[8]: test: argume

Re: Problem with test(1)

2007-04-05 Thread Tom Evans
On Thu, 2007-04-05 at 03:12 -0400, Joe Marcus Clarke wrote: > I noticed something weird with test(1) when I ran across a problem port > Makefile. Our test(1) doesn't properly check to make sure there is an > operand argument to unary operators like -f. For example: > > test -f > > Will print "T

Problem with test(1)

2007-04-05 Thread Joe Marcus Clarke
I noticed something weird with test(1) when I ran across a problem port Makefile. Our test(1) doesn't properly check to make sure there is an operand argument to unary operators like -f. For example: test -f Will print "TRUE" on FreeBSD. On Solaris, it will die: /usr/bin/test[8]: test: argume