From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] python: don't create '$(PTXCONF_SYSROOT_CROSS)/bin/python' link
Date: Sat, 1 Dec 2012 10:11:24 +0100 [thread overview]
Message-ID: <20121201091124.GL27118@pengutronix.de> (raw)
In-Reply-To: <50B9396C.3090601@gmail.com>
On Fri, Nov 30, 2012 at 04:55:40PM -0600, George McCollister wrote:
> On 11/30/2012 04:11 PM, Michael Olbrich wrote:
> >The problem is, that this link hides the system python
> >($PTXDIST_TOPDIR}/bin/python). So packages that need python for
> >building sometimes get the wrong python (if python is built first).
> >Also, I don't see why it should break you packages. There is still a
> >python in PATH.
> Breaks packages because talloc creates python bindings then tevent
> checks for talloc python bindings before building its python bindings.
> Seems like it would be a better idea to select HOST_PYTHON for packages
> that require python to build. Then the same version would always be used.
>
> Maybe I can find a clean way to force waf to use CROSS_PYTHON
Look at the other patches I've committed. Most setting
PYTHON=$(CROSS_PYTHON) in *_CONF_ENV usually helps.
michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-12-01 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 23:36 George McCollister
2012-11-30 22:11 ` Michael Olbrich
2012-11-30 22:44 ` George McCollister
2012-11-30 22:55 ` George McCollister
2012-12-01 9:11 ` Michael Olbrich [this message]
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=20121201091124.GL27118@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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