wrobell <wrob...@pld-linux.org> added the comment: looking into configure.in the above fails due to following check
AC_MSG_CHECKING(for %lld and %llu printf() format support) the check compiles and tries to _run_ a bit of software to determine lld/llu support. that of course fails (we are cross compiling). this is similar problem to ptmx/ptc problem (we do not know if host have support for ptmx/ptc). i wonder if the following would be acceptable 1. if in cross compilation mode, the configure.in could load config-cross.site. 2. the config-cross.site would define variables for ptmx/ptc, long long format and other checks which consist of running code snippets 3. appropriate checks (i.e. ptmx/ptc, lld/llu) would not be run in cross compilation mode. variables from config-cross.site would be used instead. 4. it would be a developer responsibility to set appropriate values for his platform in config-cross.site file. does above sound like a solution? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3754> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
