From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14886] Python ctypes find_library() not working correctly.
Date: Fri, 01 Jul 2022 16:55:30 +0000 [thread overview]
Message-ID: <bug-14886-163-UPQI48kXcZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14886-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14886
--- Comment #1 from Peter Scheie <pscheie@gmail.com> ---
I have seen this bug, too, in building an image for the Beaglebone Black. It
appears in the iio package in the python binding: In iio.py, CDLL calls
find_library with the argument "iio" to get the name of the libiio.so.0
library, but fails. Some folks on #beagle said using find_library() this way
was a bad idea because it produces unpredictable results (which I can attest
to). Instead, it was recommended that CDLL be called with libiio.so.0
directly, removing find_libary(). This works and I am using a patch to
implement it. BR currently uses version 0.19 of libiio but even in the most
current version, 0.24, it still uses find_library().
I tried find_library() on a few other libs and got the same None result.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-01 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 6:58 [Buildroot] [Bug 14886] New: Python ctypes find_library() not working correctly bugzilla
2022-07-01 16:55 ` bugzilla [this message]
2022-07-11 6:44 ` [Buildroot] [Bug 14886] " bugzilla
2022-07-15 0:47 ` bugzilla
2022-07-18 22:06 ` bugzilla
2022-07-20 0:49 ` bugzilla
2022-07-20 0:59 ` bugzilla
2023-03-31 18:41 ` bugzilla
2024-06-15 15:03 ` bugzilla
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=bug-14886-163-UPQI48kXcZ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.