On Thu, Jun 10, 2010 at 10:06:31PM +0100, Phil Blundell wrote:
>On Thu, 2010-06-10 at 22:50 +0200, Bernhard Reutner-Fischer wrote:
>> Both mmu and floatingpoint will need to look at COMBINED_FEATURES.
>> At least for mmu vs. !mmu PACKAGE_ARCH=${MACHINE} is unavoidable, no?
>
>I think both of those are more of a distro than a machine feature,
>really. I imagine that existing distros which are only interested in
>(i.e. only build for) MMU-equipped targets will not be very thrilled if
>their libc and/or other packages suddenly become MACHINE-specific.
If the machine does not provide a choice to use or not use the MMU then
it makes no sense to take that into account for the package arch (think
bfin or i586 or certain coldfires/m68k), yes. If, OTOH, a machine
supports it (let's say ppc) then there must at least be a nice way to
distinguish ppc<endian><mmu><floatingpoint> i would have hoped.
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
