From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: [PATCH] tools/vtpm: fix tpm_version.h error during parallel build
Date: Tue, 31 Jul 2012 10:12:36 +0200 [thread overview]
Message-ID: <870b930e816fab3180c1.1343722356@probook.site> (raw)
# HG changeset patch
# User Olaf Hering <olaf@aepfle.de>
# Date 1343722334 -7200
# Node ID 870b930e816fab3180c11c5f802e39d0f81458cb
# Parent 71c4c3dd4dfbacbfa1d57af63993eab830c8029a
tools/vtpm: fix tpm_version.h error during parallel build
Generating the tpm_version.h is not make -j safe:
In file included from ../tpm/tpm_emulator.h:25:0,
from ../tpm/tpm_startup.c:18:
../tpm/tpm_version.h:1:0: error: unterminated #ifndef
make[5]: *** [tpm_startup.o] Error 1
Fix this by calling the individual make targets because make can not
know that 'all-recursive' depends on 'version'.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
diff -r 71c4c3dd4dfb -r 870b930e816f tools/vtpm/Makefile
--- a/tools/vtpm/Makefile
+++ b/tools/vtpm/Makefile
@@ -23,7 +23,7 @@ build: build_sub
.PHONY: install
install: build
- $(MAKE) -C $(VTPM_DIR) $@
+ $(MAKE) -C $(VTPM_DIR) install-recursive
.PHONY: clean
clean:
@@ -66,7 +66,8 @@ updatepatches: clean orig
.PHONY: build_sub
build_sub: $(VTPM_DIR)/tpmd/tpmd
set -e; if [ -e $(GMP_HEADER) ]; then \
- $(MAKE) -C $(VTPM_DIR); \
+ $(MAKE) -C $(VTPM_DIR) version; \
+ $(MAKE) -C $(VTPM_DIR) all-recursive; \
else \
echo "=== Unable to build VTPMs. libgmp could not be found."; \
fi
next reply other threads:[~2012-07-31 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 8:12 Olaf Hering [this message]
2012-07-31 8:34 ` [PATCH] tools/vtpm: fix tpm_version.h error during parallel build Ian Campbell
2012-07-31 8:42 ` Ian Campbell
2012-08-02 15:54 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2012-08-02 15:53 Olaf Hering
2012-08-03 8:55 ` Ian Campbell
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=870b930e816fab3180c1.1343722356@probook.site \
--to=olaf@aepfle.de \
--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 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).