From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7628] New: Python SSL does not get built for Raspberry Pi
Date: Mon, 10 Nov 2014 10:34:02 +0000 (UTC) [thread overview]
Message-ID: <bug-7628-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7628
Summary: Python SSL does not get built for Raspberry Pi
Product: buildroot
Version: 2014.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: tobias.meggendorfer+buildroot at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I'm building for the raspberry pi and want to have the Python SSL package.
Steps i've taken:
- make distclean
- make raspberrypi_defconfig
- make nconfig
- Enable WCHAR support, python3 and python-ssl
- make
- grab coffee
However, there is no "_ssl.cpython-34m.so" ("_ssl.so" in the python2 case) to
be found in the lib-dynload folder, thus the ssl module isn't working. I'm
fairly new to (cross-)compiling so I might have missed something trivial,
although I think I've doublechecked everything. I guess there just is a include
or something like that missing, as the python compilation complains about ssl
dependencies not being found.
I've also tried this with glibc 2.18 / 2.19 and gcc 4.8 / 4.9, binutils 2.22 /
2.24 and python2 and EABIhf. I actually need glibc + EABIhf for my application,
but this problem seems to occur with every configuration.
Host: 3.2.0-70-virtual #105-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
Buildroot: git version 2014.08-0-gfcd720d
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-11-10 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 10:34 bugzilla at busybox.net [this message]
2014-11-13 23:02 ` [Buildroot] [Bug 7628] Python SSL does not get built for Raspberry Pi bugzilla at busybox.net
2014-11-13 23:14 ` bugzilla at busybox.net
2014-11-13 23:21 ` bugzilla at busybox.net
2014-11-13 23:48 ` bugzilla at busybox.net
2014-11-14 8:25 ` bugzilla at busybox.net
2014-11-14 9:06 ` bugzilla at busybox.net
2014-11-14 10:29 ` bugzilla at busybox.net
2014-11-20 17:46 ` bugzilla at busybox.net
2015-06-03 1: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-7628-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