Re: test in a m4 macro and variable created from pushdef

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Vincent Torri wrote on Sat, Aug 11, 2007 at 08:29:10PM CEST:
> On Fri, 10 Aug 2007, Ralf Wildenhues wrote:
>> * Vincent Torri wrote on Fri, Aug 10, 2007 at 07:51:00AM CEST:
>>> On Thu, 9 Aug 2007, Eric Blake wrote:
>>>
>
> Finally, I've compile autoconf (cvs). Remark that the documentation fails 
> on mingw. If you want the error, I can paste it somewhere.

I think it's merely due to the old texinfo version that comes with
MinGW.

> I've applied the patch, installed autoconf, launched autoreconf, used both 
> syntax:
>
> AM_CONDITIONAL([BUILD_DRIVER_]UP, [test "x${use_]DOWN[_driver}" = "xyes"])
> AM_CONDITIONAL([BUILD_DRIVER_]UP, test "x${[use_]DOWN[_driver]}" = "xyes")
>
> but nothing specific occurs.
>
> what should that patch do (i'm not an expert at all of m4) ?

Did you try these commands:

>>  grep UP configure
>>  grep DOWN configure

The patch changes a comment in the configure script:
  # Check whether --enable-DOWN was given.
to
  # Check whether --enable-bdf was given.

So it's rather cosmetic.

Cheers,
Ralf


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux