From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: stubdom: missing two renames
Date: Tue, 12 Feb 2008 16:56:33 +0000 [thread overview]
Message-ID: <20080212165633.GF4951@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080212154248.GE4951@implementation.uk.xensource.com>
stubdom: missing two renames
to avoid always re-compiling newlib.
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -r f3eb383d2bd5 stubdom/Makefile
--- a/stubdom/Makefile Tue Feb 12 16:51:36 2008 +0000
+++ b/stubdom/Makefile Tue Feb 12 16:54:31 2008 +0000
@@ -86,7 +86,7 @@ cross-gcc: $(GCC_STAMPFILE)
# Cross-newlib
##############
-newlib:
+newlib-cvs:
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src co -D $(NEWLIB_DATE) newlib
mv src newlib-cvs
( cd newlib-cvs && patch -p0 < ../newlib.patch)
@@ -94,7 +94,7 @@ NEWLIB_STAMPFILE=$(CROSS_ROOT)/$(GNU_TAR
NEWLIB_STAMPFILE=$(CROSS_ROOT)/$(GNU_TARGET_ARCH)-xen-elf/lib/libc.a
.PHONY: cross-newlib
cross-newlib: $(NEWLIB_STAMPFILE)
-$(NEWLIB_STAMPFILE): newlib $(GCC_STAMPFILE)
+$(NEWLIB_STAMPFILE): newlib-cvs $(GCC_STAMPFILE)
mkdir -p newlib-build
( cd newlib-build && \
CC_FOR_TARGET="$(GNU_TARGET_ARCH)-xen-elf-gcc $(TARGET_CFLAGS)" ../newlib-cvs/configure --prefix=$(CROSS_PREFIX) --verbose --target=$(GNU_TARGET_ARCH)-xen-elf --enable-newlib-io-long-long && \
next prev parent reply other threads:[~2008-02-12 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 17:40 [RFC] Add stubdomain support Samuel Thibault
2008-02-11 19:14 ` Keir Fraser
2008-02-11 19:21 ` Samuel Thibault
2008-02-11 21:23 ` Keir Fraser
2008-02-12 14:04 ` [RFC2] " Samuel Thibault
2008-02-12 14:32 ` Keir Fraser
2008-02-12 14:57 ` Samuel Thibault
2008-02-12 15:13 ` Samuel Thibault
2008-02-12 15:24 ` Keir Fraser
2008-02-12 15:42 ` Samuel Thibault
2008-02-12 16:56 ` Samuel Thibault [this message]
2008-02-13 13:32 ` Mike D. Day
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=20080212165633.GF4951@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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 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.