From: Michal Simek <monstr@monstr.eu>
To: Michal Simek <monstr@monstr.eu>,
linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au
Subject: Re: [PATCH] microblaze: Fix Makefile to delete build generated files
Date: Fri, 12 Mar 2010 11:37:34 +0100 [thread overview]
Message-ID: <4B9A196E.1040501@monstr.eu> (raw)
In-Reply-To: <20100312102040.GA7371@icd1rh0718.eee.ntu.edu.sg>
Arun Bhanu wrote:
> * Michal Simek (monstr@monstr.eu) wrote:
>> Arun Bhanu wrote:
>>> 'make mrproper' does not to delete the following build generated files:
>>> arch/microblaze/boot/linux.bin.ub
>>> arch/microblaze/boot/simpleImage.system
>>> arch/microblaze/boot/simpleImage.system.ub
>>>
>>> Fix the Makefile to delete these build generated files.
>> The problem is that if you run make clean it will delete all simpleImage
>> files too. The best will be just delete them if you run make mrproper as
>> you wrote above. Make clean should keep them or just remove .unstrip
>> because of size.
>>
>> Michal
>
> I thought 'make clean' was supposed to remove simpleImage.* files.
> PowerPC (see arch/powerpc/boot/Makefile) seems to be deleting
> simpleImage.* upon 'make clean' invocation.
It can be truth but this is Microblaze.
>
> 'make help' says:
> clean - Remove most generated files but keep the config and
> enough build support to build external modules
>
> Are the simpleImage.* files needed to build external modules? If not,
> can you explain why we should keep simpleImage.* file after a 'make
> clean' run?
nice is that there is written most files.
>
> What am I missing?
The reason is that I am configuring several platforms with different DTS
files and I am retesting that generated files. That's why I need to have
simpleImage.xxx and simpleImage.xxx.ub in boot folder which have
different names. I am doing several clean-ups but I need to store that
files.
mrproper - Remove all generated files + config + various backup files
If you look at help for mrproper we can call that files like backup files.
I agree with you that will be good to remove them but only for make
mrproper as was written in your commit message.
Michal
>
>>
>>> Signed-off-by: Arun Bhanu <arun@bhanu.net>
>>> ---
>>> arch/microblaze/boot/Makefile | 4 ++--
>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/microblaze/boot/Makefile b/arch/microblaze/boot/Makefile
>>> index 902cf98..73a3263 100644
>>> --- a/arch/microblaze/boot/Makefile
>>> +++ b/arch/microblaze/boot/Makefile
>>> @@ -62,6 +62,6 @@ quiet_cmd_dtc = DTC $@
>>> $(obj)/%.dtb: $(dtstree)/%.dts FORCE
>>> $(call if_changed,dtc)
>>> -clean-kernel += linux.bin linux.bin.gz simpleImage.*
>>> +clean-kernel += linux.bin linux.bin.gz
>>> -clean-files += *.dtb simpleImage.*.unstrip
>>> +clean-files += *.dtb *.ub simpleImage.*
>>
>> --
>> Michal Simek, Ing. (M.Eng)
>> w: www.monstr.eu p: +42-0-721842854
>> Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
>> Microblaze U-BOOT custodian
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
> -Arun
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2010-03-12 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 8:36 [PATCH] microblaze: Fix Makefile to delete build generated files Arun Bhanu
2010-03-12 8:53 ` Michal Simek
2010-03-12 10:20 ` Arun Bhanu
2010-03-12 10:37 ` Michal Simek [this message]
2010-03-12 10:56 ` Arun Bhanu
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=4B9A196E.1040501@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
/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