> 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. I know,I sent the patch only for explaining better the issue, I didn't plan at any moment to use that patch. I just wanted an howto,in order to use the site files.
> 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. I tested the default running the tests,that is to say: devshell,copy-paste the test,compile them,run them on target. > You > should use the CONFIG_SITE / site files to feed in the test result as > appropriate for the platform, That's exactly what I wanted to do,but unfortunately as I said in the first mail: *I'm not confident with it *I bet it needs review before touching it *I wouldn't know in which file I should add the changes(Maybe common-glibc?) > coupled with wrapping the AC_TRY_RUN call in > AC_CACHE_CHECK, to ensure it obeys it. I didn't know that I needed to do that, thanks a lot, I'll try to find out how to do it. Denis. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
