From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] build: fix clean rule to cover objects in unvisited subdirs
Date: Wed, 2 Dec 2015 09:22:57 +0000 [thread overview]
Message-ID: <1449048177.15768.154.camel@citrix.com> (raw)
In-Reply-To: <565DDC9002000078000BAF0C@prv-mh.provo.novell.com>
On Tue, 2015-12-01 at 09:44 -0700, Jan Beulich wrote:
> > > > On 01.12.15 at 17:34, <jonathan.creekmore@gmail.com> wrote:
> > > On Dec 1, 2015, at 10:07 AM, Jan Beulich <JBeulich@suse.com> wrote:
> > >
> > > For one build run, yes. But then you can (a) build individual object
> > > files and (b) as mentioned above change configuration (implying
> > > that you know what you're doing). Also you could, using the
> > > example above, do a kexec=y build, then a kexec=n one, then
> > > notice you needed to clean in between, so you then clean using
> > > kexec=n and build again with that option, but cleaning again
> > > would still leave the kexec files around.
> > >
> > > And btw., we have a similar issue already when you switch
> > > between arches (no cleaning happens cross-arch).
> >
> > OK, so you are working on a different assumption than I was. I was
> > treating the clean rule as needing to be run when you are wanting to
> > explicitly rebuild all object files needed for the current build
> > configuration
> > (i.e., only cleaning files that would be linked into the current
> > hypervisor
> > build).
> > It sounds like you are expecting the clean rule to clean out all object
> > files no matter whether they are part of the current build
> > configuration
> > or not.
> >
> > Working on that assumption, it seems like running a:
> > find . -name “*.o” -type f -delete
> > from the xen/ directory would accomplish that and would be less
> > fragile than trying to grab various different variables and munge
> > them to try to grab all possible .o files specified by the system.
> > Plus,
> > the find command would likely execute quicker.
> >
> > Does something like that seem acceptable?
>
> I can't see an immediate reason why it would not be, as long
> as it's clear that this won't eliminate the need to recurse into
> the subdirectories. But I'd certainly recommend to wait for
> other feedback (namely by other hypervisor maintainers)
> before you go that route.
>
> Also please note that -delete is not a standard primary, so
> would need replacing.
>
> Also the same global approach could then perhaps be used to
> remove all the .*.d files.
I can't think of a good reason not to do both of these.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-12-02 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 17:29 [PATCH] build: fix clean rule to cover objects in unvisited subdirs Jonathan Creekmore
2015-12-01 12:41 ` Jan Beulich
2015-12-01 15:52 ` Jonathan Creekmore
2015-12-01 16:07 ` Jan Beulich
2015-12-01 16:34 ` Jonathan Creekmore
2015-12-01 16:44 ` Jan Beulich
2015-12-02 9:22 ` Ian Campbell [this message]
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=1449048177.15768.154.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jonathan.creekmore@gmail.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.