All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: What's up with python3
Date: Thu, 8 Jun 2017 14:09:18 +0300	[thread overview]
Message-ID: <f510d100-faa6-d0a2-c4c8-19bf613fbc8c@linux.intel.com> (raw)
In-Reply-To: <395f03fe-7c6c-820b-5562-f98388cae49a@mlbassoc.com>

On 06/08/2017 10:28 AM, Gary Thomas wrote:
> I'm building using Poky/Yocto master
> 576821ea0a7558b626ccc87e9ae0e9ee40864956
> and I've noticed that python3 (target) is being built for my image, but it
> doesn't end up in the actual image.  None of my own recipes mention python3
> at all, yet virtually every recipe that's used in the build depend on it.
>
> I've listed all the recipes used in my build (from bitbake -g =>
> recipe-depends.dot)
> and sucked out the ones that claim to depend on python3.  I don't see
> why, for
> example, python(2) depends on python3?
>
> Can someone explain this?  I've added the appropriate files to this email.
>
> I'm mostly curious, but also a bit concerned that my builds are doing more
> than they need (and hence just taking longer than they might need to)

Typically for two reasons:

a) a recipe needs to execute python during build, and host python is not 
suitable for some reason - so native python is built and used;

b) a supplementary package needs python, while the main package does not 
- most often this is the -ptest package, which will not end up in the 
image, unless you ask.

Alex



  reply	other threads:[~2017-06-08 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08  7:28 What's up with python3 Gary Thomas
2017-06-08 11:09 ` Alexander Kanavin [this message]
2017-06-08 11:13   ` Gary Thomas
2017-06-08 11:52 ` Burton, Ross
2017-06-08 12:10   ` Gary Thomas
2017-06-08 12:31     ` Burton, Ross

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=f510d100-faa6-d0a2-c4c8-19bf613fbc8c@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.org \
    /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.