From: Blue Swirl <blauwirbel@gmail.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Makefile: add fsdev/*.{o,d} to clean
Date: Sat, 3 Jul 2010 07:16:16 +0000 [thread overview]
Message-ID: <AANLkTimHMSB-9SFm6NcuqUFYikS6rPoH19Fbj250Y2BY@mail.gmail.com> (raw)
In-Reply-To: <4C2D86ED.4080108@jp.fujitsu.com>
On Fri, Jul 2, 2010 at 6:27 AM, Hidetoshi Seto
<seto.hidetoshi@jp.fujitsu.com> wrote:
> (2010/07/02 4:48), Blue Swirl wrote:
>> 2010/7/1 Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>:
>>> There were fsdev/qemu-fsdev.{o,d} not removed at "make clean".
>>>
>>> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
>>> ---
>>> Makefile | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/Makefile b/Makefile
>>> index 560eac6..ce5f0e6 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -159,7 +159,7 @@ clean:
>>> # avoid old build problems by removing potentially incorrect old files
>>> rm -f config.mak op-i386.h opc-i386.h gen-op-i386.h op-arm.h opc-arm.h gen-op-arm.h
>>> rm -f *.o *.d *.a $(TOOLS) TAGS cscope.* *.pod *~ */*~
>>> - rm -f slirp/*.o slirp/*.d audio/*.o audio/*.d block/*.o block/*.d net/*.o net/*.d
>>> + rm -f {slirp,audio,block,net,fsdev}/*.{o,d}
>>
>> Not every shell out there support {}:
>> dash -c 'echo {a,b}*.c'
>> {a,b}*.c
>>
>> bash -c 'echo {a,b}*.c'
>> acl.c aes.c aio.c alpha-dis.c arch_init.c arm-dis.c arm-semi.c async.c
>> balloon.c block-migration.c block.c blockdev.c bt-host.c bt-vhci.c
>> buffered_file.c
>
> You are right, but I found that Makefile already has:
>
> 169 distclean: clean
> (snip)
> 174 rm -f qemu-{doc,tech}.{info,aux,cp,dvi,fn,info,ky,log,pdf,pg,toc,tp,vr}
>
> So then is it better to rewrite this line not to use {} ...?
Yes, a patch for that would be nice.
next prev parent reply other threads:[~2010-07-03 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 3:32 [Qemu-devel] [PATCH] Makefile: add fsdev/*.{o,d} to clean Hidetoshi Seto
2010-07-01 19:48 ` Blue Swirl
2010-07-02 6:27 ` Hidetoshi Seto
2010-07-03 7:16 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-08 5:26 Hidetoshi Seto
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=AANLkTimHMSB-9SFm6NcuqUFYikS6rPoH19Fbj250Y2BY@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).