I just tried configuring libxml2 which has
AC_PATH_PROG(RM, rm, /bin/rm)
in its configure.in. After running configure
rm: libtoolT: No such file or directory
Done configuring
Probably from
cfgfile="${ofile}T"
trap "$RM \"$cfgfile\"; exit 1" 1 2 15
[adding bug-libtool, replies can drop autoconf]
On 07/29/2010 10:26 AM, Patrick Welche wrote:
> I just tried configuring libxml2 which has
>
> AC_PATH_PROG(RM, rm, /bin/rm)
>
> in its configure.in. After running configure
>
> rm: libtoolT: No such file or directory
> Done conf
Hi,
I am trying to maintain a package (NCO) with some possibly arcane
or obsolete autoconf/m4 usage. One macro started breaking a year or
two ago and I do not know how to fix it. The autoconf macro that
is breaking is called NCO_CHECK_FUNCS. It is intended to be used
in configure.in thusly:
NCO_C
On 07/27/2010 12:26 PM, Charlie Zender wrote:
> Here is the definition of NCO_CHECK_FUNCS in acinclude.m4:
>
> AC_DEFUN([NCO_CHECK_FUNCS],
> [AC_FOREACH([AC_Func],[$1],
You should consider naming your variable outside of the AC namespace, in
case autoconf uses the macro AC_Func as an internal det
Eric,
I immediately tested your simpler definition of NCO_CHECK_FUNCS.
It seems to work as advertised, and eliminates many warnings
which aclocal and autoheader issued for the last few years.
Phew.
If someone could email me the location of the archives
of this mailing list, I would greatly apprec
On 07/29/2010 01:02 PM, Charlie Zender wrote:
> Eric,
>
> I immediately tested your simpler definition of NCO_CHECK_FUNCS.
> It seems to work as advertised, and eliminates many warnings
> which aclocal and autoheader issued for the last few years.
> Phew.
>
> If someone could email me the locatio
Le 29/07/2010 12:12, Eric Blake a écrit :
> On 07/29/2010 01:02 PM, Charlie Zender wrote:
>> Eric,
>>
>> I immediately tested your simpler definition of NCO_CHECK_FUNCS.
>> It seems to work as advertised, and eliminates many warnings
>> which aclocal and autoheader issued for the last few years.
>>
