From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Matthias_Wei=DFer?= Date: Wed, 29 Jun 2011 17:00:58 +0200 Subject: [U-Boot] Removal of generated asm-offsets.s/h In-Reply-To: <20110629142002.16F53158D11C@gemini.denx.de> References: <4E0B3331.9030605@arcor.de> <20110629142002.16F53158D11C@gemini.denx.de> Message-ID: <4E0B3E2A.4040409@arcor.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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