Hi Stepan,
* Stepan Kasal wrote on Tue, May 31, 2005 at 08:30:03PM CEST:
On Tue, May 31, 2005 at 05:27:08PM +0200, Ralf Wildenhues wrote:
Note also that some compilers won't error out on unknown flags (esp
Intel ones :) but only issue a warning. This may or may not matter for
you. If it
On Wed, 2005-06-01 at 13:45 -0400, Dan Manthey wrote:
On Wed, 1 Jun 2005, Ralf Corsepius wrote:
On Wed, 2005-06-01 at 18:33 +0200, Stepan Kasal wrote:
I think the best solution is to drop caching from programs.m4.
Only over my dead body ;-)
Caching was invented mainly for
Hello Dan,
On Wed, Jun 01, 2005 at 01:45:49PM -0400, Dan Manthey wrote:
By the way, note that there seems to be some confusion about whether a
PROG variable is set. `PROG=' does _not_ unset it. How does
AC_CHECK_PROG behave when the variable is set to the empty string?
it usestest x$VAR
Hi Ralf,
On Wed, Jun 01, 2005 at 07:08:08PM +0200, Ralf Corsepius wrote:
On Wed, 2005-06-01 at 18:33 +0200, Stepan Kasal wrote:
Caching was invented mainly for expensive tests which involve
calling a compiler, which can be really slow.
No, caching had been invented for faster interaction of
On Thu, 2 Jun 2005, Stepan Kasal wrote:
it usestest x$VAR = x
Thus the manual should use the term is nonempty, not is set.
(One of the reasons for this behaviour is that unset is not portable.)
It's documented that the builtin `unset' is non-portable, but what about
the use of unset
