[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_PROG_CC problems on Windows with MKS Shell

From: Akim Demaille
Subject: Re: AC_PROG_CC problems on Windows with MKS Shell
Date: 17 Jan 2001 10:13:58 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Crater Lake)

>>>>> "Lars" == Lars J Aas <address@hidden> writes:

Lars> A better fix would be to have AC_PATH_PROG (or whichever macro
Lars> it is that searches for the compiler) to also consider implied
Lars> exe- extensions on systems that use them, and add the extension
Lars> to the returned program name.

The real good fix will be to use test -x IMHO.  This ought to work in
this case, right?

But I don't want $ac_test_x, this is too bad a change.  My goal is
test='missing test' or something like this for tests that don't
support -x.

Likewise for `which -a'.  This should release us from handling the
PATH separator.  This are details which would clobber Autoconf way too
much, we must put them in a lower layer.

OTOH, if we do this, we lose portability in M4sh, which would be very
bad :(

reply via email to

[Prev in Thread] Current Thread [Next in Thread]