From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: CPU type .config <-> i386/Makefile question[s]
Date: Sun, 5 Jun 2005 20:43:56 +0100 [thread overview]
Message-ID: <200506052043.56547.nick@linicks.net> (raw)
In-Reply-To: <20050605174322.GF4992@stusta.de>
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..."
prev parent reply other threads:[~2005-06-05 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 13:58 CPU type .config <-> i386/Makefile question[s] Nick Warne
2005-06-05 17:43 ` Adrian Bunk
2005-06-05 19:43 ` Nick Warne [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506052043.56547.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.