On Sun, Mar 28, 2010 at 9:44 AM, Denis 'GNUtoo' Carikli <[email protected]>wrote:
> > btoc(m4 macro)'s AC_TRY_RUN didn't handle the cross-compilation case. > thanks ? for telling me that the third argument > was for cross-compilation. Using the third argument for this sort of thing is not ideal.. in fact, I've experimented with patching the autoconf macros to disable it. The only time you should consider using it is when the test is only for a sanity check, and its result does not affect behavior. When the result does affect behavior and clearly isn't a sanity check, setting an assumed default knowing nothing about the target environment is not the way to go. You should use the CONFIG_SITE / site files to feed in the test result as appropriate for the platform, coupled with wrapping the AC_TRY_RUN call in AC_CACHE_CHECK, to ensure it obeys it. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
