Re: Question: Configuration Header Templates

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

 



According to Jeffrey Walton on 2/14/2010 9:12 PM:
> In configure.ac, I have the following:
> dnl bignums
> AC_ARG_ENABLE([bignum-forcing], AS_HELP_STRING([--enable-bignum-forcing],
>   [Force the usage of the 64 bits bignum ...]),
>   [force_bignums=$enableval], [force_bignums=no])

You are missing some m4 quoting.  That should be:

AC_ARG_ENABLE([bignum-forcing], [AS_HELP_STRING([--enable-bignum-forcing],
  [Force the usage of the 64 bits bignum ...])],
  [force_bignums=$enableval], [force_bignums=no])

> if test "x$force_bignums" = "xyes"; then
>    AC_DEFINE([PDF_FORCE_BIGNUMS],[0],[Force the usage of the 64 bits
> bignum ...])
> fi

Typically, you would AC_DEFINE a macro to 1, not 0, when a feature is
being enabled.

> After bootstrap/configure, this produces (in config.h):
> /* Force the usage of the 64 bits bignum ... */
> /* #undef PDF_FORCE_BIGNUMS */

That is typical behavior for when a feature was not selected.

> What I'm looking for (notice the a #define is used, and the define is
> commented):
> /* Force the usage of the 64 bits bignum ... */
> /* #define PDF_FORCE_BIGNUMS */

There is no way to result in a commented #define in config.h.  It is
either a commented #undef or an uncommented #define.  Maybe we need to
take a step back, and ask why you think you need a commented #define to
result in config.h?  Also, are you sure you are testing the use of
'./configure --enable-bignum-forcing'?

-- 
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@xxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
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