On Thu, 2010-07-08 at 23:36 +0800, Holger Freyther wrote:
> E.g. a recipe not honoring our CPPFLAGS might silently pass this check
> (while before it was hardcoded into the compiler). My proposal would be
> to extend the sanity check and grep the compile log for gcc and -ibad
> and fail if gcc exists but -ibad does not occur?
That sounds a bit fragile too. How about just adding the -ibad flags to
${CC} rather than putting them in CPPFLAGS? Only the most determined
package is likely to be able to build without using our value for CC.
Failing that, I guess the original approach of patching the compiler is
actually the better one, inelegant though it might seem.
p.
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
