Garrett Cooper <yaneg...@gmail.com> added the comment: Ok. Taking a look at trunk...
The following could be converted to AC_TRY_COMPILE statements for the 3rd AC_TRY_RUN tuple: 1. $ac_enable_profiling : 697 2. $ac_cv_no_strict_aliasing_ok : 921 3. $ac_cv_opt_olimit_ok : 1070 4. $ac_cv_olimit_ok : 1092 5. $ac_cv_pthread_is_default : 1126 6. $ac_cv_kpthread : 1163 7. $ac_cv_pthread : 1225 8. $ac_osx_32bit : 1569 9. $ac_cv_pthread_system_supported : 2229 10. $ac_cv_have_size_t_format : 3959 The following can just be converted to AC_TRY_COMPILE: 1. $ipv6 : 2278 2. $ac_cv_have_chflags : 2663 3. $ac_cv_have_lchflags : 2693 The following will need to be sorted out, as to what needs to be done here, as they are legitimate runtime only tests: 1. $ac_cv_little_endian_double : 3249 2. $ac_cv_big_endian_double : 3271 3. $ac_cv_mixed_endian_double : 3299 4. $ac_cv_x87_double_rounding : 3354 5. $ac_cv_broken_sem_getvalue : 3395 6. $ac_cv_tanh_preserves_zero_sign : 3430 7. $ac_cv_wchar_t_signed : 3510 8. $ac_cv_rshift_extends_sign : 3597 9. $ac_cv_broken_nice : 3714 10. $ac_cv_broken_poll : 3735 11. $ac_cv_working_tzset : 3772 Taking a look at py3k, most of the offsets are the same -- some have changed, but the only the test which doesn't exist in trunk is the following: 1. $ac_cv_broken_mbstowcs : 3872 Again, this is a valid runtime test, so it needs to be sorted out what should be done here with cross-compilation. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1006238> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
