From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ewan Mellor <ewan@xensource.com>,
Anthony Liguori <aliguori@us.ibm.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: Re: [PATCH] add check for python-devel to tools build
Date: Wed, 22 Nov 2006 09:10:09 +0100 [thread overview]
Message-ID: <456413F1.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20061121172319.GI30929@leeni.uk.xensource.com>
Keir - will you integrate this, or should I re-post a patch?
>>> Ewan Mellor <ewan@xensource.com> 21.11.06 18:23 >>>
On Tue, Nov 21, 2006 at 05:10:43PM +0000, Daniel P. Berrange wrote:
> On Tue, Nov 21, 2006 at 05:06:49PM +0000, Ewan Mellor wrote:
> > On Tue, Nov 21, 2006 at 10:51:49AM -0600, Anthony Liguori wrote:
> >
> > > Jan Beulich wrote:
> > > >Again, this must be given exec permission after applying.
> > > >
> > > >Signed-off-by: Jan Beulich <jbeulich@novell.com>
> > > >
> > > >Index: 2006-11-17/tools/check/check_python_devel
> > > >===================================================================
> > > >--- /dev/null 1970-01-01 00:00:00.000000000 +0000
> > > >+++ 2006-11-17/tools/check/check_python_devel 2006-11-21
> > > >12:03:08.000000000 +0100
> > > >@@ -0,0 +1,13 @@
> > > >+#!/bin/bash
> > > >+# CHECK-BUILD
> > > >+
> > > >+function error {
> > > >+ echo
> > > >+ echo " *** Check for python development environment FAILED"
> > > >+ exit 1
> > > >+}
> > > >+
> > > >+lib=lib
> > > >+test "$(uname -m)" != x86_64 || lib=lib64
> > > >+set -e
> > > >+[ -e /usr/$lib/python/config/Makefile ] || error
> > >
> > > There is no /usr/lib/python/config/Makefile on Ubuntu. You should be
> > > okay if you also check for /usr/lib/python-2.[345]/config/Makefile.
> >
> > My Debian box has /usr/lib/python2.3. How about
> > /usr/lib/python*/config/Makefile? That should be OK, and has the advantage of
> > including /usr/lib/python.
>
> Using wildcards though will not be reliable. eg I have both python 2.3 and 2.4
> installed, but python 2.4 is the version I'm deploying Xen against. This test
> won't catch the case where I have python-devel = 2.3, but don't have the
> python-devel == 2.4 installed. We want to make sure we only check against the
> version we're actually building against.
python -c '
import os.path, sys
for p in sys.path:
if os.path.exists(p + "/config/Makefile"):
sys.exit(0)
sys.exit(1)
'
Ewan.
next prev parent reply other threads:[~2006-11-22 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 16:45 [PATCH] add check for python-devel to tools build Jan Beulich
2006-11-21 16:48 ` Daniel P. Berrange
2006-11-21 16:51 ` Anthony Liguori
2006-11-21 17:06 ` Ewan Mellor
2006-11-21 17:10 ` Daniel P. Berrange
2006-11-21 17:23 ` Ewan Mellor
2006-11-22 8:10 ` Jan Beulich [this message]
2006-11-22 9:20 ` 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=456413F1.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=aliguori@us.ibm.com \
--cc=berrange@redhat.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.