From: "Jan Beulich" <jbeulich@novell.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] yet another package check (take 2)
Date: Fri, 15 Dec 2006 08:22:06 +0000 [thread overview]
Message-ID: <4582693E.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20061214171113.GB3748@leeni.uk.xensource.com>
>>> Ewan Mellor <ewan@xensource.com> 14.12.06 18:11 >>>
>On Thu, Dec 14, 2006 at 04:23:32PM +0000, Jan Beulich wrote:
>
>> As before, the file added to tools/check/ must be given exec permission.
>>
>> Now using the approach suggested by Christoph Egger <Christoph.Egger@amd.com>.
>>
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>>
>> Index: 2006-12-11/tools/Makefile
>> ===================================================================
>> --- 2006-12-11.orig/tools/Makefile 2006-12-04 08:49:57.000000000 +0100
>> +++ 2006-12-11/tools/Makefile 2006-12-14 14:25:02.000000000 +0100
>> @@ -36,7 +36,7 @@ all: check
>> $(MAKE) ioemu
>>
>> .PHONY: install
>> -install: check
>> +install: check_install
>> @set -e; for subdir in $(SUBDIRS-y); do \
>> $(MAKE) -C $$subdir $@; \
>> done
>> @@ -58,6 +58,10 @@ distclean: clean
>> check:
>> $(MAKE) -C check
>>
>> +.PHONY: check_install
>> +check_install: check
>> + $(MAKE) -C check install
>> +
>> .PHONY: check_clean
>> check_clean:
>> $(MAKE) -C check clean
>
>What's this change for? In tools/check/Makefile, it says not to run make -C
>check install as part of make install.
Hmm, I didn't realize this was intentionally not used. For me it simply means I
can't run Xen tools directly out of the build area (since install.sh does nothing
but copying things around, there's little point in using it for other than an
install into the default (root=/) location. But obviously, when run directly out
of the build area, the install checks will never get done and I'm ending up
with a cryptic error message again.
As I can't think of a smarter way, I think taking this change will depend on
whether it's acceptable to the majority to require all install prerequisites to
be present on build-only machines, and whether it is a reasonable
expectation that at some future point it'll be possible to run multiple Xen
versions on the same machine (and, as per above comment, directly out of
the build area).
Jan
next prev parent reply other threads:[~2006-12-15 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 16:23 [PATCH] yet another package check (take 2) Jan Beulich
2006-12-14 16:47 ` Ewan Mellor
2006-12-14 16:59 ` Jan Beulich
2006-12-14 17:04 ` Ewan Mellor
2006-12-14 17:11 ` Ewan Mellor
2006-12-15 8:22 ` Jan Beulich [this message]
2006-12-15 9:33 ` Ewan Mellor
2006-12-15 9:49 ` Keir Fraser
2006-12-15 9:50 ` Jan Beulich
2006-12-15 9:54 ` Keir Fraser
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=4582693E.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Christoph.Egger@amd.com \
--cc=ewan@xensource.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 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.