Hello Ralf,
On 01.08.2010 18:58, Ralf Wildenhues wrote:
> Hi Rainer,
>
> * Rainer Tammer wrote on Sun, Aug 01, 2010 at 05:09:01PM CEST:
>> this are the failures of autoconf 2.67 make check on AIX V7BETA:
>>
>> 213: AC_CACHE_CHECK FAILED (base.at:478)
>> 240: Signal handling F
* Karl Berry wrote on Mon, Aug 02, 2010 at 12:00:21AM CEST:
> Autoconf 2.66 added '+' to the set of allowed characters in --enable-*
>
> Why?
So gnulib could have --enable-c++.
> So, my question is: could standards.texi document the set of allowed
> characters?
>
> Can you make a pr
Autoconf 2.66 added '+' to the set of allowed characters in --enable-*
Why?
So, my question is: could standards.texi document the set of allowed
characters?
Can you make a proposal?
Current Autoconf has -+. mapped to _ and otherwise wants characters
eligible for shell variab
Hi Rainer,
* Rainer Tammer wrote on Sun, Aug 01, 2010 at 05:09:01PM CEST:
> this are the failures of autoconf 2.67 make check on AIX V7BETA:
>
> 213: AC_CACHE_CHECK FAILED (base.at:478)
> 240: Signal handling FAILED (torture.at:1263)
>
> I have included the testsuite.log for
Hello,
this are the failures of autoconf 2.67 make check on AIX V7BETA:
213: AC_CACHE_CHECK FAILED (base.at:478)
240: Signal handling FAILED (torture.at:1263)
I have included the testsuite.log for a detailed reference.
Are this known problem?
Bye
Rainer
testsuite.log.
Hello bug-standards readers,
Autoconf 2.66 added '+' to the set of allowed characters in --enable-*
and --with-* switches (mapping them to underscores for the variable name
that they influence). Using these can cause problems in trees with
older configures, or ones not made by Autoconf that are n
