From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Removal of generated asm-offsets.s/h
Date: Wed, 29 Jun 2011 17:00:58 +0200 [thread overview]
Message-ID: <4E0B3E2A.4040409@arcor.de> (raw)
In-Reply-To: <20110629142002.16F53158D11C@gemini.denx.de>
Am 29.06.2011 16:20, schrieb Wolfgang Denk:
> Dear =?ISO-8859-15?Q?Matthias_Wei=DFer?=,
>
> In message<4E0B3331.9030605@arcor.de> you wrote:
>>
>> If a soc automatically generates asm-offsets.s/h in its makefile it
>> isn't removed by a make clean or make distclean. See mx35 as an example.
>> Even adding a clean: target to the SoCs makefile doesn't help. What
>> would be the right way to remove these files with make clean?
>
> Add it to the list of files to remove in the top level Makefile?
Well, thats is not that easy. The generated asm-offsets.h file ends up
in arch/arm/include/asm/arch-mx35/ after a "make mx35pdk_config" "make"
"make distclean" run. It is generated to include/asm/arch/ in the SoCs
makefile so I don't understand why it ends up in
arch/arm/include/asm/arch-mx35/
I don't think it makes sense to add a entry for each SoC using auto
generated asm-offset files to the top level makefile. Same goes for the
.s file as we shouldn't remove all .s files in the tree.
Matthias
next prev parent reply other threads:[~2011-06-29 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 14:14 [U-Boot] Removal of generated asm-offsets.s/h Matthias Weißer
2011-06-29 14:20 ` Wolfgang Denk
2011-06-29 15:00 ` Matthias Weißer [this message]
2011-06-29 15:48 ` Stefano Babic
2011-06-29 18:37 ` Matthias Weisser
2011-06-30 7:09 ` Stefano Babic
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=4E0B3E2A.4040409@arcor.de \
--to=weisserm@arcor.de \
--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 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.