On Tue, Jul 26, 2011 at 3:02 PM, Kumar Gala <[email protected]> wrote: > > On Jul 26, 2011, at 11:18 AM, Richard Purdie wrote: > >>>> You're already found the way to pass configuration to *libc using values >>>> in TARGET_FPU to pickup the right configuration. >>>> >>>> Is there a use case we're missing? >>> >>> Yes, for [e]glibc we have optimized libc functions for a given / >>> specific PPC processor. So we need someway to tell configure this. >> >> I'd do this by looking for flags in TUNE_FEATURES as Mark has also >> mentioned. >> >> Cheers, >> >> Richard > > Are we thinking something like the following in e[glibc] recipes: > > EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppce500mc", > "-with-cpu=e500mc", "", d)}" >
I guess we can make a python function since most architectures can benefit from --with-cpu > - k > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
