From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with Python ctypes on Raspberry Pi platfform - Was: Re: [PATCH v2 1/1] python-pyusb: new package
Date: Mon, 28 Oct 2013 20:47:23 +0100 [thread overview]
Message-ID: <20131028204723.458fbe10@skate> (raw)
In-Reply-To: <CAMduVEcp4u0Xb5tSK=LV_s5E2jGF501R_eKjWFnOUWtcTZ4URw@mail.gmail.com>
Dear Wojciech Zabolotny,
On Sat, 26 Oct 2013 17:30:16 +0200, Wojciech Zabolotny wrote:
> Testing the newly created python-pyusb on a Raspberry Pi platform, I
> have found, that it doesn't work.
> Investigating the problem more thoroughly, I have found that it is
> associated with Python ctypes package, which is not able to locate the
> libraries.
> Analyzing the Python-2.7.3/Lib/ctypes/util.py file, I have found, that
> on that platform, when neither gcc nor binutils are installed on
> target (which is typical for small systems), locating of the library
> relies on output of the "ldconfig -p" command.
> Unfortunately, this command returns simply:
>
> # /sbin/ldconfig -p
> Library cache disabled
>
> I'm afraid that this problem may affect many other programs and
> packages relying on Python ctypes... (and probably not only on
> Raspberry Pi platform)
Interesting. Can you post a simple example of ctypes usage that
exhibits the problem?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-28 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 15:30 [Buildroot] Problems with Python ctypes on Raspberry Pi platfform - Was: Re: [PATCH v2 1/1] python-pyusb: new package Wojciech Zabolotny
2013-10-28 17:34 ` Wojciech Zabolotny
2013-10-28 19:47 ` Thomas Petazzoni [this message]
2013-10-28 20:29 ` Wojciech Zabolotny
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=20131028204723.458fbe10@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox