From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] host-python-2.7 failure to build _hashlib
Date: Tue, 28 Jan 2020 10:14:31 +0100 [thread overview]
Message-ID: <20200128101431.02251042@windsurf> (raw)
In-Reply-To: <CA+h21hr2ReX5zxqmRrM9dq77S-nwqSQvmTQh6N-FLEvoooUfLw@mail.gmail.com>
Hello Vladimir,
On Tue, 28 Jan 2020 01:39:57 +0200
Vladimir Oltean <olteanv@gmail.com> wrote:
> > Because we don't enforce this for host packages. We do enforce it for
> > target packages (i.e a target package cannot be built if its Config.in
> > option is not enabled somehow). But we don't enforce it for host
> > packages.
> >
> > For example, host-pkgconf has a visible Config.in option called
> > BR2_PACKAGE_HOST_PKGCONF. However, almost none of the packages that
> > depend on host-pkgconf have a select BR2_PACKAGE_HOST_PKGCONF.
> >
>
> Why not?
That's mainly historical. We used to not have any visible Config.in
option for host packages: host packages were only built as build
dependencies of target packages. But then, we realized that some host
packages were not just mere build dependencies of target packages: they
were useful by themselves. This is the case for flashing tools,
debugging tools, filesystem image creation utilities, and more. So we
started adding Config.in options for host packages.
We have been considering adding Config.in options for all host packages
(some visible, some hidden), but adding all those "select" was
considered too much of a burden compared to the benefit.
We had some discussion about this at a previous Buildroot Developers
meeting, after FOSDEM 2019. See the notes of the discussion:
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2019#.22Config.in.host.22_for_all_host_packages.
> > > - The Makefile doesn't complain that they don't (usually it does, when
> > > packages add _DEPENDENCIES that are absent from Config.in)
> >
> > See above: only for target packages.
> >
> > > When I enable BR2_PACKAGE_HOST_PYTHON and BR2_PACKAGE_HOST_PYTHON_SSL
> > > in .config, I am able to carry on with the build.
> > >
> > > Can somebody please explain what is going on?
> > > I am not a proficient Python user either, by the way.
> >
> > I don't really understand why your host-python package fails to build.
> > Could you share the entire build log of the host-python package ?
> >
>
> So it looks like the mailing list didn't like my log pasted in here.
> Let's try Github gists:
> https://gist.github.com/vladimiroltean/4d6b1441b0dbe64dc8e2f9d1ce336e42
We're not explicitly disabling building the hashlib module when
building host-python, and hashlib needs OpenSSL, but apparently the
OpenSSL of your system is not compatible with Python 2.x.
Could you try the following change ?
diff --git a/package/python/python.mk b/package/python/python.mk
index 41a981e3d3..cd79be78f6 100644
--- a/package/python/python.mk
+++ b/package/python/python.mk
@@ -33,7 +33,8 @@ HOST_PYTHON_CONF_OPTS += \
--disable-test-modules \
--disable-bz2 \
--disable-ossaudiodev \
- --disable-pyo-build
+ --disable-pyo-build \
+ --disable-hashlib
# Make sure that LD_LIBRARY_PATH overrides -rpath.
# This is needed because libpython may be installed at the same time that
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-28 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 22:35 [Buildroot] host-python-2.7 failure to build _hashlib Vladimir Oltean
2020-01-27 22:40 ` Thomas Petazzoni
2020-01-27 23:39 ` Vladimir Oltean
2020-01-28 9:14 ` Thomas Petazzoni [this message]
2020-01-28 10:28 ` Vladimir Oltean
2020-01-28 13:44 ` Thomas Petazzoni
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=20200128101431.02251042@windsurf \
--to=thomas.petazzoni@bootlin.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