From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python: fix building _hashlib of host-python
Date: Thu, 20 Jul 2017 13:09:39 +0200 [thread overview]
Message-ID: <20170720130939.1b22a471@windsurf> (raw)
In-Reply-To: <CAO6UsjD3rv0Vg2GJM0JwELO_TnT2gt-DEt0hsTxRxvu5faTVNw@mail.gmail.com>
Hello,
On Thu, 20 Jul 2017 18:59:31 +0800, Diankun Zhang wrote:
> From https://packages.ubuntu.com/xenial/amd64/openssl/filelist, we can see
> the openssl package on ubuntu 16.04 does not cotain the libssl or
> licrypto.so,
> instead they are in package libssl1.0.0,
> https://packages.ubuntu.com/xenial/amd64/libssl1.0.0/filelist.
libssl is a *binary* package that is produced from the source package
openssl.
> In most of systems nowadays, openssl (and libssl ) is installed since the
> hash algorithms are needed to meet kinds of requirements.
Yes, the libraries, but not necessarily the development files.
> Yes, I'm using the pyang tool on my host to compile some YANG files. The
> compiled YANG files are platform independent ideally.
OK.
So, again what is needed is a hidden BR2_PACKAGE_HOST_PYTHON_OPENSSL
that enables OpenSSL support in host-python, which the pyang package
could select.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-20 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 7:33 [Buildroot] [PATCH 1/1] package/python: fix building _hashlib of host-python Diankun Zhang
2017-07-20 7:56 ` Thomas Petazzoni
2017-07-20 8:21 ` Diankun Zhang
2017-07-20 8:27 ` Thomas Petazzoni
2017-07-20 9:09 ` Diankun Zhang
2017-07-20 9:19 ` Thomas Petazzoni
2017-07-20 10:59 ` Diankun Zhang
2017-07-20 11:09 ` Thomas Petazzoni [this message]
2017-07-20 11:20 ` Diankun Zhang
2017-07-20 11:24 ` Thomas Petazzoni
2017-07-20 11:39 ` Diankun Zhang
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=20170720130939.1b22a471@windsurf \
--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