From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] tools: python portability fixes
Date: Tue, 28 Jul 2009 09:34:42 +0200 [thread overview]
Message-ID: <200907280934.42860.Christoph.Egger@amd.com> (raw)
In-Reply-To: <19053.63640.992395.149945@mariner.uk.xensource.com>
On Monday 27 July 2009 20:57:28 Ian Jackson wrote:
> Christoph Egger writes ("[PATCH] tools: python portability fixes"):
> > Attached patch applies portability fixes for NetBSD:
>
> Hi. As Keir says, I'm away, but:
> > - remove useless get-path. It is a bash specific script which tries to
> > gain information the build system already has.
> > - make install-wrap work with bourne shell on NetBSD
> > - pass `which $(PYTHON)` to install-wrap. It is safe to assume
> > this always works because in case it doesn't the build system
> > errors out very early in tools/check/check_python
>
> Isn't the effect of this to stop substituting #!/usr/bin/python2.5 (or
> whatever) for #!/usr/bin/python ? In which case it's wrong as I've
> already explained.
No, the effect is this:
When $(PYTHON) is python you get #!/usr/bin/python,
when $(PYTHON) is python2.5 you get #!/usr/bin/python2.5,
when $(PYTHON) is python2.6 you get #!/usr/bin/python2.6,
when $(PYTHON) is /usr/bin/python2.4 you get #!/usr/bin/python2.4,
etc.
When you install python on NetBSD, you don't have a "python"
binary. You always have pythonN.M where N.M is the version number
so you can have multiple python versions installed.
On NetBSD, you actually get #!/usr/pkg/bin/python2.5.
The get-path is a bash specific script which tries to get the information
`which $(PYTHON)` already provides but doesn't work for the case
where "python" doesn't exist.
The current approach is doomed to always fail on NetBSD.
On Linux you have a python symlink to pythonN.M.
Remove the symlink manually, build and install xen with
gmake PYTHON=pythonN.M and you can reproduce the issue on Linux.
The patch fixes it.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-07-28 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 13:58 [PATCH] tools: python portability fixes Christoph Egger
2009-07-23 14:06 ` Keir Fraser
2009-07-27 18:57 ` Ian Jackson
2009-07-28 7:34 ` Christoph Egger [this message]
2009-07-28 9:55 ` Ian Jackson
2009-07-28 12:27 ` Christoph Egger
2009-08-04 10:32 ` Ian Jackson
2009-08-04 12:33 ` Christoph Egger
2009-08-04 13:03 ` Ian Jackson
2009-08-04 13:40 ` Christoph Egger
2009-08-04 14:20 ` John Levon
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=200907280934.42860.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@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 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.