From: Andi Kleen <andi@firstfloor.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: arch/x86_64/kernel/Makefile: why EXTRA_AFLAGS := -traditional
Date: Thu, 20 Sep 2007 16:09:54 +0200 [thread overview]
Message-ID: <20070920140954.GI18707@one.firstfloor.org> (raw)
In-Reply-To: <200709201501.44009.vda.linux@googlemail.com>
On Thu, Sep 20, 2007 at 03:01:43PM +0100, Denys Vlasenko wrote:
> Hi Andi,
>
> arch/x86_64/kernel/Makefile has
>
> EXTRA_AFLAGS := -traditional
>
> and this is causing me trouble with #define MACRO(a,b) a.b
> (defined in one of included header file).
> It expands incorrectly, as "a. b" - extra space.
>
> If I use a.##b, all other .S files suffer - I am getting
> a.##b expansion in them.
>
> Can I remove EXTRA_AFLAGS := -traditional?
Inherited long ago from i386. Does it build without it?
If yes it's ok to remove.
-Andi
prev parent reply other threads:[~2007-09-20 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 14:01 arch/x86_64/kernel/Makefile: why EXTRA_AFLAGS := -traditional Denys Vlasenko
2007-09-20 14:09 ` Andi Kleen [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=20070920140954.GI18707@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda.linux@googlemail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox