Hi,
On Fri, Jul 01, 2005 at 11:34:09AM -0700, Paul Eggert wrote:
> > * lib/autoconf/c.m4 (AC_PROG_CC_C_O): Use conf$$.o instead of
...
> That looks good, except for one thing: the command
OK, I'll fix the patch before committing it.
> rm -f conf$$*
>
> might remove a bit too much. For e
Hello,
On Fri, Jul 01, 2005 at 03:33:55PM -0700, Paul Eggert wrote:
> > P.S. I've just noticed that autoconf/aclocal.m4 also holds
> > AM_MISSING_HAS_RUN. Why? To avoid dependencies?
>
> Yes; someone who's installing Autoconf shouldn't need Automake,
> to avoid the usual bootstrapping problems.
Stepan Kasal wrote:
> Hello,
>
> On Fri, Jul 01, 2005 at 10:14:28AM +0200, Harald Dunkel wrote:
>
>>How can I tell autoconf to not use -c and -o together,
>>regardless what the test said?
>
>
> Do I guess correctly that you in fact use AM_PROG_CC_C?
AM_PROG_CC_C_O. Yup.
> Then the following h
The attached patch is necessary as if you set the environment variable M4
to "m4 --nesting-limit=2048", the regexp won't match as there is a '='
rather than a ' ' after nesting-limit.
BTW if even 2048 is too small what could be wrong with my configure
script? (In fact this is apr, at the autoheade
Stepan Kasal <[EMAIL PROTECTED]> writes:
> The main problem is in the trap defined in ./lib/autoconf/general.m4
> in _AC_INIT_PREPARE:
>
> rm -f -r conftest* confdefs* conf$[$]* $ac_clean_files
How about if you simply remove conf[0-9]* instead? Those file names
are all reserved by Autoconf
Patrick Welche <[EMAIL PROTECTED]> writes:
> The attached patch is necessary as if you set the environment variable M4
> to "m4 --nesting-limit=2048", the regexp won't match as there is a '='
> rather than a ' ' after nesting-limit.
>
> BTW if even 2048 is too small what could be wrong with my con
