Re: CPU type .config <-> i386/Makefile question[s]

[Nick Warne <nick@linicks.net>]

On Sunday 05 June 2005 18:43, Adrian Bunk wrote:

> the specific reason is that kernel 2.4 is in a maintainance mode and
> such changes are not considered being worth the risk of breaking
> anything anywhere with any of the supported gcc versions.
>
> In kernel 2.6, this is already handled the way you expect it.
>
> > Also I notice that if I changed the top level Makefile to include my
> > specific CPU, then the i386/Makefile adds += -march=i686 to the build
> > lines AFTER CFLAGS~ thus the second one will take precedence (I guess)
> > anyway, and the -march CFLAG changes are basically over-ridden?
>
> Users are not expected to manually set any CFLAGS.
>
> It might work in your case, but unless you _really_ know what you are
> doing you always risk some breakage.

I see!  Thanks for info.  I can do my own patch to play with :-)

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/