[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: what is $ac_t ?
From: |
Sam Steingold |
Subject: |
Re: what is $ac_t ? |
Date: |
Fri, 17 Sep 2010 13:23:46 -0400 |
On Fri, Sep 17, 2010 at 12:36 PM, Eric Blake <address@hidden> wrote:
>
> Really, anyone with $ac_t in their script should modernize, and use ECHO_T
> instead.
http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/src/m4/proto.m4
I think I will just drop it altogether:
@@ -16,8 +16,7 @@ AC_DEFUN([CL_PROTO],
AC_CACHE_VAL(cl_cv_proto_[$1], [$2
cl_cv_proto_$1="$3"])
cl_cv_proto_$1=`echo "[$]cl_cv_proto_$1" | tr -s ' ' | sed -e 's/( /(/'`
-AC_MSG_RESULT([$]{ac_t:-
- }[$]cl_cv_proto_$1)
+AC_MSG_RESULT([$]cl_cv_proto_$1)
])
dnl CL_PROTO_RET(INCLUDES, DECL, CACHE-ID, TYPE-IF-OK, TYPE-IF-FAILS)
>> 2. required: is there a replacement for ac_t or should it be dropped?
>
> Yes, we can avoid using $ac_t for our temporary variable name, to respect
> the fact that there are some _really_ old scripts that are exploiting
> formerly undocumented internals that no longer exist. Although those
> configure.in should be modernized, we can at least make their output look
> prettier with a simple change to avoid the problematic name.
I suggest that you set ac_t to something like "fix your configure.ac:
ac_t is obsolete, use ECHO_T instead".
--
Sam Steingold <http://sds.podval.org>