All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] host-python-2.7 failure to build _hashlib
Date: Mon, 27 Jan 2020 23:40:31 +0100	[thread overview]
Message-ID: <20200127234031.79371041@windsurf> (raw)
In-Reply-To: <CA+h21hors57FFbQzm0x2Rd_pABb95-GaxPOPiRQ5ZzB9NgT-Mg@mail.gmail.com>

Hello Vladimir,

On Tue, 28 Jan 2020 00:35:49 +0200
Vladimir Oltean <olteanv@gmail.com> wrote:

> Ok, but I have to ask: why is host-python even built at all? For one
> thing, BR2_PACKAGE_HOST_PYTHON is not set.
> But with "make graph-depends", I am able to see that host-python is
> dragged in by:
> - python itself, which I selected
> - host-python-setuptools (dragged in by python-lxml, which I selected)
> - host-nodejs (dragged in by nodejs, which I selected)

Right, host-python is a dependency of all those things indeed.

> Granted, I don't know much, but I'm baffled that:
> - None of the above 3 packages select BR2_PACKAGE_HOST_PYTHON in their Config.in

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.

> - 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 ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-27 22:40 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 [this message]
2020-01-27 23:39   ` Vladimir Oltean
2020-01-28  9:14     ` Thomas Petazzoni
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=20200127234031.79371041@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 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.