From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13166] New: python-rpi-gpio: does not work against aarch64, unintentional side-effect of gcc-10 patch
Date: Wed, 19 Aug 2020 22:12:18 +0000 [thread overview]
Message-ID: <bug-13166-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13166
Bug ID: 13166
Summary: python-rpi-gpio: does not work against aarch64,
unintentional side-effect of gcc-10 patch
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: christian at paral.in
CC: buildroot at uclibc.org
Target Milestone: ---
python-rpi-gpio on aarch64 (pi 4):
ImportError:
/usr/lib/python3.8/site-packages/RPi/_GPIO.cpython-38-aarch64-linux-gnu.so:
undefined symbol: high
There is a patch attached to the package -
fixes the "multiple definition of" errors with gcc10
Signed-off-by: Michael Fischer <mf@go-sys.de>
It changes the "high" variable to be "extern" which might have caused this?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-19 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 22:12 bugzilla at busybox.net [this message]
2020-08-19 22:20 ` [Buildroot] [Bug 13166] python-rpi-gpio: does not work against aarch64, unintentional side-effect of gcc-10 patch bugzilla at busybox.net
2020-08-19 22:31 ` bugzilla at busybox.net
2020-08-19 22:32 ` bugzilla at busybox.net
2020-08-20 21:09 ` bugzilla at busybox.net
2020-08-20 21:30 ` bugzilla at busybox.net
2020-08-20 22:24 ` bugzilla at busybox.net
2020-08-20 22:25 ` bugzilla at busybox.net
2020-08-20 23:33 ` bugzilla at busybox.net
2020-08-23 21:31 ` bugzilla at busybox.net
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-13166-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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