> I've messed this up. I *do* get the test statement to fail, but > it carries on anyway, because of the leading - sign. I've done this:
Ah, I never said that the test fails, but looking at my previous message
I have to admit that it sounds so.
[...]
> I can't find a GNU autoconf macro to test for test, preferring a GNU
> version. That would usually work. I found this:
I do not think it's necessary. '-e' tests if file exits, but this option
is not supported by solaris /bin/sh (but it is supported by ksh and
bash). I suggested using '-x' instead, which tests if file exists and is
executable, and which is supported even by /bin/sh.
> $ /bin/sh -c '[ -e /bin/ls ] && echo exists'
> /bin/sh: test: argument expected
> $ /bin/bash -c '[ -e /bin/ls ] && echo exists'
> exists
> $ /bin/ksh -c '[ -e /bin/ls ] && echo exists'
> exists
> OK, all the same as yours. What's happening here?
From the solaris man page
=============================== test(1) ================================
...
-e file True if file exists. (Not avail-
able in sh.)
...
========================================================================
I just suggest changing '-x' for '-e'. But the tests are running fine
even without this change.
Sorry for the confusion.
--
Vlad
pgpI5ucDCrxMY.pgp
Description: PGP signature
