[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: expr ... and `expr ...` return different results on QNX 4.2.5
From: |
Lars J. Aas |
Subject: |
Re: expr ... and `expr ...` return different results on QNX 4.2.5 |
Date: |
Fri, 1 Dec 2000 13:32:50 +0100 |
User-agent: |
Mutt/1.2.5i |
On Thu, Nov 30, 2000 at 04:28:13PM -0500, Pavel Roskin wrote:
: Hello!
:
: > Yes. I wouldn't bother doing that. Just tell them to get a working
: > shell. You have to draw the line somewhere.
:
: That's correct. We cannot support command.com anyway :-)
...darn - I was just about to start a `comfigure' branch... ;)
: How about this:
:
: ac_output=`command || echo "===ERROR==="`
: case $ac_output in
: *===ERROR===)
: AC_MSG_ERROR([command failed]) ;;
: *) ;;
: esac
How about something like this:
ac_output=`command`
command >/dev/null 2>/dev/null
The second re-run ought to be conditional on this problem to optimize the
configure script, so if someone knows how to write a condition test that won't
affect $?, raise your voice (keyboard)...
Lars J
- Re: expr ... and `expr ...` return different results on QNX 4.2.5,
Lars J. Aas <=