Op 27 mei 2011, om 01:33 heeft Richard Purdie het volgende geschreven: > On Thu, 2011-05-26 at 13:41 -0700, [email protected] wrote: > >> --- >> meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb | 3 +++ >> 1 files changed, 3 insertions(+), 0 deletions(-) >> >> diff --git a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb >> b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb >> index b77df2c..051bd72 100644 >> --- a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb >> +++ b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb >> @@ -17,3 +17,6 @@ PE = "1" >> PR = "r0" >> >> EXTRA_OECONF += "--with-driver=xlib" >> + >> +# nullify -O2 >> +CFLAGS_append += " -O" > > I talked about this on IRC but simply put, no way. > > The problem is: > > a) Arm specific > b) determined now to be armv7 specific > c) gcc version specific > > and the fix should reflect this. > > So ideally when we select gcc 4.6 in tcmode-default.inc we should add > something there which adds a work around for mesa-xlib. > > I've suggested something like: > > TARGET_CC_ARCH_arm_pn-mesa-xlib := > "${@'${TARGET_CC_ARCH}'.replace('armv7','armv5')}" > > which whilst ugly, should do what we need it to.
So how do I opt out of that? I don't use gcc 4.6 and suddenly mesa gets compiled for a suboptimal architecture. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
