All of lore.kernel.org
 help / color / mirror / Atom feed
* What's up with python3
@ 2017-06-08  7:28 Gary Thomas
  2017-06-08 11:09 ` Alexander Kanavin
  2017-06-08 11:52 ` Burton, Ross
  0 siblings, 2 replies; 6+ messages in thread
From: Gary Thomas @ 2017-06-08  7:28 UTC (permalink / raw)
  To: yocto@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

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)

Thanks for any pointers

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: task-depends.dot --]
[-- Type: application/msword-template, Size: 885461 bytes --]

[-- Attachment #3: recipe-depends.dot --]
[-- Type: application/msword-template, Size: 135805 bytes --]

[-- Attachment #4: pn-buildlist --]
[-- Type: text/plain, Size: 2514 bytes --]

popt-native
file
libffi-native
board-framework
libevent
libtool
initscripts
opkg-utils-native
mklibs-native
gcc-source-6.3.0
nspr
elfutils
can-utils
glibc-initial
glibc-locale
libsolv
shadow-securetty
zlib
net-tools
run-postinsts
gcc-cross-arm
perl-native
update-rc.d
gcc-cross-initial-arm
texinfo-dummy-native
packagegroup-amltd-usbhost
libxml2-native
libarchive
bash-completion
ntp
glib-2.0-native
kern-tools-native
gtk-doc-native
zlib-native
base-files
iptables
python-subprocess32
shadow-native
iproute2
gmp
openssl-native
strace
openssl
cross-localedef-native
dbus
glibc
packagegroup-amltd-i2c
gperf-native
libarchive-native
bzip2-native
udev-extraconf
init-ifupdown
libsolv-native
binutils-native
rsync
usbutils
mtd-utils
kmod-native
python3
tar
ncurses
libpcre-native
xinetd
unifdef-native
bison-native
attr
qemuwrapper-cross
eudev
libcap
installer
gettext
xproto-native
libpcre
packagegroup-amltd-can
gdbm-native
lrzsz
sqlite3-native
u-boot-fw-utils
gdbm
modutils-initscripts
rpm
util-linux
bzip2
alsa-lib-native
perl
u-boot-mkimage-native
makedepend-native
libpng-native
tcp-wrappers
pps-tools
libmpc-native
gettext-minimal-native
db
packagegroup-amltd-ubifs
nss-native
gcc-runtime
libxslt-native
update-rc.d-native
packagegroup-amltd-installer
kmod
u-boot-mkimage
shadow
opkg-utils
amltd-feed-config-opkg
nss
depmodwrapper-cross
popt
readline
dosfstools
nand-installer
busybox
ldconfig-native
cryptodev-linux-native
curl-native
quilt-native
coreutils
netbase
iperf
python3-native
libgcc
nspr-native
lzo-native
libsocketcan
openssh
glib-2.0
util-macros-native
automake-native
imx-kobs
m4-native
packagegroup-amltd-nand
libgcc-initial
linux-libc-headers
devmem2
pkgconfig-native
db-native
file-native
python-ptyprocess
bc-native
cmake-native
bash
python-native
opkg
pigz-native
libtool-native
netkit-tftp
opkg-native
expat
acl
sqlite3
gettext-native
qemu-native
e2fsprogs-native
python
attr-native
elfutils-native
ethtool
shadow-sysroot
binutils-cross-arm
e2fsprogs
pbzip2-native
opkg-arch-config
util-linux-native
sysvinit
sysvinit-inittab
prelink-native
libusb-compat
cryptodev-linux
readline-native
linux-boundary
watchdog-config
xz
lzo
xz-native
rpm-native
i2c-tools
libusb1
watchdog
pixman-native
flex-native
parted
gnu-config-native
expat-native
base-passwd
python-setuptools-native
libtool-cross
dbus-native
esc-testing-image
ncurses-native
mpfr-native
gmp-native
dtc-native
lzop-native
production-tests
python-pexpect
pseudo-native
libxml2
autoconf-native
makedevs-native
libffi
packagegroup-amltd

[-- Attachment #5: python3.depends --]
[-- Type: text/plain, Size: 1159 bytes --]

"bash-completion" -> "python3"
"bash" -> "python3"
"board-framework" -> "python3"
"busybox" -> "python3"
"bzip2" -> "python3"
"coreutils" -> "python3"
"dbus" -> "python3"
"e2fsprogs" -> "python3"
"elfutils" -> "python3"
"esc-testing-image" -> "python3"
"eudev" -> "python3"
"glib-2.0" -> "python3"
"init-ifupdown" -> "python3"
"initscripts" -> "python3"
"installer" -> "python3"
"iproute2" -> "python3"
"kmod" -> "python3"
"libarchive" -> "python3"
"libpcre" -> "python3"
"libsolv" -> "python3"
"libtool" -> "python3"
"libxml2" -> "python3"
"lrzsz" -> "python3"
"modutils-initscripts" -> "python3"
"mtd-utils" -> "python3"
"ncurses" -> "python3"
"netkit-tftp" -> "python3"
"net-tools" -> "python3"
"ntp" -> "python3"
"openssh" -> "python3"
"opkg" -> "python3"
"opkg-utils" -> "python3"
"parted" -> "python3"
"python" -> "python3"
"python-subprocess32" -> "python3"
"readline" -> "python3"
"rpm" -> "python3"
"run-postinsts" -> "python3"
"shadow" -> "python3"
"sysvinit" -> "python3"
"tar" -> "python3"
"u-boot-fw-utils" -> "python3"
"udev-extraconf" -> "python3"
"usbutils" -> "python3"
"util-linux" -> "python3"
"watchdog" -> "python3"
"xinetd" -> "python3"

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: What's up with python3
  2017-06-08  7:28 What's up with python3 Gary Thomas
@ 2017-06-08 11:09 ` Alexander Kanavin
  2017-06-08 11:13   ` Gary Thomas
  2017-06-08 11:52 ` Burton, Ross
  1 sibling, 1 reply; 6+ messages in thread
From: Alexander Kanavin @ 2017-06-08 11:09 UTC (permalink / raw)
  To: Gary Thomas, yocto@yoctoproject.org

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: What's up with python3
  2017-06-08 11:09 ` Alexander Kanavin
@ 2017-06-08 11:13   ` Gary Thomas
  0 siblings, 0 replies; 6+ messages in thread
From: Gary Thomas @ 2017-06-08 11:13 UTC (permalink / raw)
  To: Alexander Kanavin, yocto@yoctoproject.org

On 2017-06-08 13:09, Alexander Kanavin wrote:
> 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;

Not that: I filtered out all uses of python3-native - these are only *target* dependencies

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

None of my recipes build -ptest stuff:
   $ find tmp/deploy/ipk/ -name "*ptest*"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: What's up with python3
  2017-06-08  7:28 What's up with python3 Gary Thomas
  2017-06-08 11:09 ` Alexander Kanavin
@ 2017-06-08 11:52 ` Burton, Ross
  2017-06-08 12:10   ` Gary Thomas
  1 sibling, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2017-06-08 11:52 UTC (permalink / raw)
  To: Gary Thomas; +Cc: yocto@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 474 bytes --]

On 8 June 2017 at 08:28, Gary Thomas <gary@mlbassoc.com> wrote:

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

I'm 90% sure that this all comes through opkg-utils being the provider for
update-alternatives.

You could verify this by disabling the python PACKAGECONFIG in opkg-utils.

Ross

[-- Attachment #2: Type: text/html, Size: 952 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: What's up with python3
  2017-06-08 11:52 ` Burton, Ross
@ 2017-06-08 12:10   ` Gary Thomas
  2017-06-08 12:31     ` Burton, Ross
  0 siblings, 1 reply; 6+ messages in thread
From: Gary Thomas @ 2017-06-08 12:10 UTC (permalink / raw)
  To: yocto

On 2017-06-08 13:52, Burton, Ross wrote:
> 
> On 8 June 2017 at 08:28, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
> 
>     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?
> 
> 
> I'm 90% sure that this all comes through opkg-utils being the provider for update-alternatives.
> 
> You could verify this by disabling the python PACKAGECONFIG in opkg-utils.

I'm impressed!  That eliminated all of them :-)

What would I lose by do this, in general, as it's pretty obvious
that python3 is not needed by any of the recipes I use?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: What's up with python3
  2017-06-08 12:10   ` Gary Thomas
@ 2017-06-08 12:31     ` Burton, Ross
  0 siblings, 0 replies; 6+ messages in thread
From: Burton, Ross @ 2017-06-08 12:31 UTC (permalink / raw)
  To: Gary Thomas; +Cc: yocto@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

On 8 June 2017 at 13:10, Gary Thomas <gary@mlbassoc.com> wrote:

> What would I lose by do this, in general, as it's pretty obvious
> that python3 is not needed by any of the recipes I use?
>

It's the scripts in opkg-utils, so if you're not installing that in your
image then you won't notice at all.

(looks like the recipe should respect the python PACKAGECONFIG and delete
the python scripts so they can't get packaged)

Ross

[-- Attachment #2: Type: text/html, Size: 874 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-06-08 12:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-06-08  7:28 What's up with python3 Gary Thomas
2017-06-08 11:09 ` Alexander Kanavin
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

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.