This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients xdegaye
Date 2019-03-06.16:03:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551888207.23.0.560311387445.issue36214@roundup.psfhosted.org>
In-reply-to
Content
When the AC_RUN_IFELSE macro is used as the 'COMMANDS-TO-SET-IT' argument of the AC_CACHE_VAL or AC_CACHE_CHECK macros, it is possible to override the last argument of AC_RUN_IFELSE that is used when cross-compiling and set the variable with a cached value instead.

The determination of the following variables in configure.ac does not follow this mechanism (does not use AC_CACHE_VAL et al):

ac_osx_32bit, ac_cv_x87_double_rounding, have_glibc_memmove_bug, have_ipa_pure_const_bug

This should be changed except for the cases where cross-compilation does not make sense.
History
Date User Action Args
2019-03-06 16:03:27xdegayesetrecipients: + xdegaye
2019-03-06 16:03:27xdegayesetmessageid: <1551888207.23.0.560311387445.issue36214@roundup.psfhosted.org>
2019-03-06 16:03:27xdegayelinkissue36214 messages
2019-03-06 16:03:27xdegayecreate