[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reverse AC_REQUIRE and AC_CHECK_TYPE changes?
From: |
Akim Demaille |
Subject: |
Re: Reverse AC_REQUIRE and AC_CHECK_TYPE changes? |
Date: |
04 Aug 2001 16:01:47 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Academic Rigor) |
>>>>> "Adam" == Adam J Richter <address@hidden> writes:
Adam> AC_DEFUN(REQUIRE_FOO,[AC_REQUIRE(FOO)]); AC_REQUIRE_FOO
>> Why? Just run FOO.
Adam> Because many of your macros generate warnings or even abort if
Adam> they are called more than once and many user macros may have
Adam> undesired side effects
Such as?
IMHO, these macros have to be fixed, instead of being workaround.
Adam> and, of course, will result in slower ./configure run time if
Adam> they are called more than once,
Agreed, but that's trying to optimize things. Unfortunately the
Autoconf framework is not robust enough to let the user try to
optimize. Each time someone tried, it eventually appeared to be
broken.
Adam> making use of autoconf less desirable in comparison to
Adam> alternatives.
Definitely.