mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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: Fri, 30 Nov 2012 23:11:04 +0100	[thread overview]
Message-ID: <20121130221104.GJ27118@pengutronix.de> (raw)
In-Reply-To: <CAFSKS=MRw+1mNc6WMtDv6w9iLvuk6vmkLQuxFSokMtG6MQ_0KA@mail.gmail.com>

Hi,

On Thu, Nov 29, 2012 at 05:36:21PM -0600, George McCollister wrote:
> Why did you decide to remove this link? This breaks several of my
> package rules that use the waf build system. Specifically talloc and
> tevent. Is there a case when you don't want to use CROSS_PYTHON? If
> you did this to solve a specific problem let me know because I was
> having some python related problems until I applied the attached
> patch. Maybe you ran into this as well.

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.

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

  reply	other threads:[~2012-11-30 22: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 [this message]
2012-11-30 22:44   ` George McCollister
2012-11-30 22:55   ` George McCollister
2012-12-01  9:11     ` Michael Olbrich

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=20121130221104.GJ27118@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