From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
"lars.kurth@citrix.com" <lars.kurth@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: Xen 4.9 rc6
Date: Tue, 23 May 2017 17:46:44 +0100 [thread overview]
Message-ID: <22820.26484.604702.71074@mariner.uk.xensource.com> (raw)
In-Reply-To: <8f82471c-7549-8e74-ca34-d5fce55bf9b5@arm.com>
Julien Grall writes ("Re: [Xen-devel] Xen 4.9 rc6"):
> On 23/05/17 10:24, M A Young wrote:
> > I had build problems with these two patches added (and before I added
> > them). It looks like at the stage in my build process where
> > make -j2 prefix=/usr tools
> > gets run it is running
> > make -C tools/include install
> > make -C tools/include dist
> > together and it fails soon after when the alignment checks run at the same
> > time.
I think this is happening because, in xen.git/Makeefile:
dist-tools: dist-tools-public-headers
dist-%: DESTDIR=$(DISTDIR)/install
dist-%: install-%
@: # do nothing
install-tools: build-tools-public-headers
So make thinks it can try to `build' the targets
build-tools-public-headers and dist-tools-public-headers
simultaneously.
The problem here is that
1. /Makefile needs to invoke each subdirectory exactly
once, not multiple times, or they come in parallel
2. /Makefile is (now) confused about when it should
handle the relationship between different targets for
the same subcomponent, and when the subdirectory
Makefile is supposed to do that.
The rule for (2) used to be:
/Makefile converts make dist to DESTDIR=... make install
for all other targets, /Makefile's make <target>-<subdir>
passes the <target> to <subdir> and does not consider
what <target> might mean and whether it ought to imply
some other targets in subdir.
I think therefore that maybe this can fixed by:
* Dropping the `dist-tools' dependency on dist-tools-p.-h.
* Replacing the `install-tools' dependency by one on
install-tools-p-h.
* Replacing the rules for *-public-headers with something
like
%-tools-public-headers:
$(MAKE) -C tools/include $*
Does this sound plausible ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-23 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 18:09 Xen 4.9 rc6 Julien Grall
2017-05-23 9:24 ` M A Young
2017-05-23 11:25 ` Julien Grall
2017-05-23 16:46 ` Ian Jackson [this message]
2017-05-24 16:11 ` Ian Jackson
2017-05-24 16:14 ` [PATCH for-4.9 1/2] tools/include/Makefile: Support `build' target Ian Jackson
2017-05-25 13:59 ` Roger Pau Monné
2017-05-24 16:14 ` [PATCH for-4.9 2/2] Makefile: Regularise subdir targets and their dependencies Ian Jackson
2017-05-24 17:14 ` Andrew Cooper
2017-05-24 21:42 ` Michael Young
2017-05-25 12:15 ` Julien Grall
2017-05-25 14:05 ` Roger Pau Monné
2017-05-25 15:45 ` Ian Jackson
2017-05-25 15:49 ` Julien Grall
2017-05-25 15:50 ` Roger Pau Monné
2017-05-25 12:42 ` Xen 4.9 rc6 [and 1 more messages] Ian Jackson
2017-05-25 12:55 ` Julien Grall
2017-05-25 12:59 ` Andrew Cooper
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=22820.26484.604702.71074@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xenproject.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.