On Thu, Jun 10, 2010 at 01:27:36PM -0700, Chris Larson wrote:
>On Thu, Jun 10, 2010 at 1:22 PM, Phil Blundell <[email protected]> wrote:
>> If you start factoring MACHINE_FEATURES into that kind of decision then,
>> logically, the package needs to have PACKAGE_ARCH=${MACHINE}. I don't
>> think it would be a very good thing to start forcing packages down that
>> path unnecessarily.
This is unavoidable for certain special setups, isn't it.
>
>
>Fair enough, that seems reasonable for this particular case. Now that you
>bring it up, we adjust package arch to machine when we use a machine
>specific file:// file, but maybe we need to teach it to check for references
>to MACHINE_FEATURES or COMBINED_FEATURES, somehow.
Both mmu and floatingpoint will need to look at COMBINED_FEATURES.
At least for mmu vs. !mmu PACKAGE_ARCH=${MACHINE} is unavoidable, no?
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
