From: Daniel Kiper <daniel.kiper@oracle.com>
To: ian.jackson@eu.citrix.com, jbeulich@suse.com,
stefano.stabellini@eu.citrix.com, xen-devel@lists.xensource.com
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Subject: [PATCH 2/3] stubdom: Do not create dangling links
Date: Wed, 24 Jul 2013 16:06:38 +0200 [thread overview]
Message-ID: <1374674799-16465-3-git-send-email-daniel.kiper@oracle.com> (raw)
In-Reply-To: <1374674799-16465-1-git-send-email-daniel.kiper@oracle.com>
There is not architecture dependent files in libxc
hence do not create dangling links.
Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
(based on commit c2eea87c43d1617b2c15c57fce9a64a436679fca)
---
stubdom/Makefile | 5 -----
1 file changed, 5 deletions(-)
diff --git a/stubdom/Makefile b/stubdom/Makefile
index e7db7b5..303416e 100644
--- a/stubdom/Makefile
+++ b/stubdom/Makefile
@@ -257,11 +257,6 @@ mk-headers-$(XEN_TARGET_ARCH): ioemu/linkfarm.stamp
ln -sf $(XEN_ROOT)/tools/libxc/*.h . && \
ln -sf $(XEN_ROOT)/tools/libxc/*.c . && \
ln -sf $(XEN_ROOT)/tools/libxc/Makefile . )
- mkdir -p libxc-$(XEN_TARGET_ARCH)/$(XEN_TARGET_ARCH)
- [ -h libxc-$(XEN_TARGET_ARCH)/$(XEN_TARGET_ARCH) ] || ( cd libxc-$(XEN_TARGET_ARCH)/$(XEN_TARGET_ARCH) && \
- ln -sf $(XEN_ROOT)/tools/libxc/$(XEN_TARGET_ARCH)/*.c . && \
- ln -sf $(XEN_ROOT)/tools/libxc/$(XEN_TARGET_ARCH)/*.h . && \
- ln -sf $(XEN_ROOT)/tools/libxc/$(XEN_TARGET_ARCH)/Makefile . )
$(CROSS_MAKE) -C $(MINI_OS) links
touch mk-headers-$(XEN_TARGET_ARCH)
--
1.7.10.4
next prev parent reply other threads:[~2013-07-24 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:06 [PATCH 0/3] Build system fixes for Xen 4.1.6 Daniel Kiper
2013-07-24 14:06 ` [PATCH 1/3] stubdom: Clean extras/mini-os directory during make clean Daniel Kiper
2013-07-24 14:06 ` Daniel Kiper [this message]
2013-07-24 14:06 ` [PATCH 3/3] Silently ignore include errors during make distclean Daniel Kiper
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=1374674799-16465-3-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).