From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] libxcb: fix path to Python modules
Date: Thu, 06 May 2010 10:59:18 +0200 [thread overview]
Message-ID: <87vdb19zix.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <ea5d9f4196b6fdcd1fc55428c058b1d83b430591.1273096504.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 5 May 2010 23:55:16 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> When building libxcb, the variable XCBPROTO_XCBPYTHONDIR must point to
Thomas> the location where the Python modules needed to run the c_client.py
Thomas> program are installed. The path
Thomas> $(STAGING_DIR)/usr/lib/python2.6/site-packages was hardcoded. However,
Thomas> it doesn't work when the version of Python installed on the host is
Thomas> Python 2.5.
So we depend on python being available on the host? Shouldn't we just
use the hostpython stuff we already have and E.G
$(PYTHON_VERSION_MAJOR)?
Alternatively we should probably add a check in libxcb.mk and print an
$(error if it isn't there.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-05-06 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 21:55 [Buildroot] [pull request] Pull request for branch misc-fixes Thomas Petazzoni
2010-05-05 21:55 ` [Buildroot] [PATCH 1/3] busybox: disable MTD utils in default configuration Thomas Petazzoni
2010-05-05 21:55 ` [Buildroot] [PATCH 2/3] libxcb: fix path to Python modules Thomas Petazzoni
2010-05-06 8:59 ` Peter Korsgaard [this message]
2010-05-06 9:17 ` Thomas Petazzoni
2010-05-06 9:55 ` Peter Korsgaard
2010-05-05 21:55 ` [Buildroot] [PATCH 3/3] xlib_libX11: re-add a patch to fix the keysymdef issue Thomas Petazzoni
2010-05-07 22:05 ` [Buildroot] [pull request] Pull request for branch misc-fixes Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2010-05-07 19:30 Thomas Petazzoni
2010-05-07 19:30 ` [Buildroot] [PATCH 2/3] libxcb: fix path to Python modules Thomas Petazzoni
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=87vdb19zix.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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.