Hello Mike, all, * Mike Frysinger writes: > > the issue does go beyond this specific fs test as there are a bunch of common > vars that come from gnulib that do not get set properly in cross-compiling > (like the silly GNU malloc(0) / rpl_malloc test) ... perhaps start with > gnulib and have some common m4 file spit out a notice for people when they're > doing cross-compiling to visit some document for further info ... not sure > what sort of mechanism would exist though for automatically extracting and > documenting though ... i can dabble in m4, but it's certainly not a strong > point of mine
This idea has some appeal to it. Not sure whether another optional argument to AC_RUN_IFELSE for explanation would be the best. But for a start you can get a good idea of runtime issues using this command to show the cross-compile settings of macros: autoconf '--trace=AC_TRY_RUN:$f:$l:$4' '--trace=AC_RUN_IFELSE:$f:$l:$4' Hope that helps. Please Cc: me on replies. Cheers, Ralf _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
