public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM preprocessor error generating assembly dependencies
Date: Mon, 31 Aug 2009 15:00:15 +0200	[thread overview]
Message-ID: <4A9BC95F.1000306@googlemail.com> (raw)
In-Reply-To: <4A9BC756.1080906@googlemail.com>

Dirk Behme wrote:
> Wolfgang Denk wrote:
>>> Any expert here could have look to which options are taken for ARM's 
>>> assembly dependency generation? It seems to me that -D__ASSEMBLY__ is 
>>> missing there?
>>
>> I have no clue what you are talking about...
> 
> It seems to me that dependencies for ARM assembly files are generated 
> with different (incomplete?) options than the compilation is done. That 
> is, it seems to me that for ARM assembly file compilation, 
> -D__ASSEMBLY__ is set, while for dependency generation it isn't.
> 
> I'm asking if anybody can give me a hint where I have to look for the 
> (compiler/assembler) options used for dependency generation (for 
> lib_arm/*.S for lib_arm/.depend) or if any expert likes to have a look 
> to this (most probably being faster than me then ;) ).

Example: Put

#ifndef __ASSEMBLY__
#error "Foo"
#endif

into a lib_arm/*.S file you like (and which is build ;)) and test what 
happens. I would assume, if -D__ASSEMBLY__ is used everywhere 
correctly, no error message should be given.

Best regards

Dirk

  reply	other threads:[~2009-08-31 13:00 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 [this message]
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

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=4A9BC95F.1000306@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