On 19/02/2006 11:50, Ralf Wildenhues wrote:
Hi Julien,
* Julien Lecomte wrote on Sun, Feb 19, 2006 at 01:49:45AM CET:
if ( ($1) || exit) >/dev/null 2>&1 && \
( (cd $srcdir && $1) || exit) >/dev/null 2>&1; then
Note: the '|| exit' may seem like overkill, but I copied those two lines
from another autoconf macro. This may be to avoid a long lost documented
shell bug.
*snip*
So if there is no other, yet unknown reason to add `|| exit', and you
have not found a shell where both `pwd -W' and the others trigger a
segfault, _and_ the segfault may be suppressed with `|| exit', then you
may safely delete it. No need to add to legends.
Noted.
Going back to your original question: what about the much simpler
approach I suggested, which would avoid all of these issues?
Yes, I'm sorry I didn't get back to this earlier.
The suggestion rules out the fact that it may be legit to have a file
called 'configure' or 'configure.gnu' in the building directory.
Although I wouldn't recommend having such a file, I think it shouldn't
be arbitrarily ruled out.
Now we could take both: if 'configure' or 'configure.gnu' exists, then
do the extra checking.
Julien
_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
