From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM preprocessor error generating assembly dependencies
Date: Tue, 01 Sep 2009 09:57:47 +0200 [thread overview]
Message-ID: <4A9CD3FB.708@googlemail.com> (raw)
In-Reply-To: <20090901073409.A90EB834A950@gemini.denx.de>
Dear Wolfgang Denk,
Wolfgang Denk wrote:
> Dear Dirk Behme,
>
> In message <4A9CC333.7020403@googlemail.com> you wrote:
>>>> That is, it doesn't use AFLAGS set in config.mk to generate assembly
>>>> dependencies? So setting -D__ASSEMBLY__ while generating assembly
>>>> dependencies is missing here?
>>> It's not needed. At least for none of the files in mainline.
>> Does this mean you will accept a patch that removes -D__ASSEMBLY__
>> from AFLAGS in config.mk?
>
> Probablky not, as this seems to be bogus and would most probably break
> a ton of things.
>
> What I mean is that I am not aware of any __ASSEMBLY__ related issues
> with dependency generation in mainline code, so I fail to understand
> which exact problem you are trying to solve.
I think it's not a good idea to calculate dependencies with different
options than used for compilation. So the exact problem I'm looking
for is to use same options for (assembly file) dependency generation
and compilation. Just to be clean here, independent of a discussion
whether it might be necessary or not (which would be obsolete then).
Best regards
Dirk
prev parent reply other threads:[~2009-09-01 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 8:39 [U-Boot] ARM preprocessor error generating assembly dependencies Dirk Behme
2009-08-31 10:40 ` Wolfgang Denk
2009-08-31 12:51 ` Dirk Behme
2009-08-31 13:00 ` Dirk Behme
2009-09-01 6:13 ` Dirk Behme
2009-09-01 6:38 ` Wolfgang Denk
2009-09-01 6:46 ` Dirk Behme
2009-09-01 7:34 ` Wolfgang Denk
2009-09-01 7:57 ` Dirk Behme [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=4A9CD3FB.708@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/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