From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] About python2 and python3
Date: Mon, 9 May 2016 23:00:51 +0200 [thread overview]
Message-ID: <5730FA83.9000608@gmail.com> (raw)
In-Reply-To: <20160509222604.25fa27a8@free-electrons.com>
Il 09/05/2016 22:26, Thomas Petazzoni ha scritto:
> So, I think we'll stick with just supporting the installation of
> either Python 2 or Python 3. I'd rather recommend you to see why you
> need Python 2 at all, and try to see if you can make that part work
> with Python 3.
Ok, it's reasonable.
Is there an easy way to find out which package(s) is selecting another?
I had to copy & paste several times the loooong "selected by" line:
> Selected by:
>
> BR2_PACKAGE_KODI [=n] &&
> BR2_INSTALL_LIBSTDCPP [=y] &&
> BR2_HOST_GCC_AT_LEAST_4_6 [=y] &&
> BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 [=y] &&
> BR2_TOOLCHAIN_HAS_THREADS [=y] &&
> !BR2_TOOLCHAIN_USES_MUSL [=n] &&
> (BR2_PACKAGE_KODI_EGL_GLES [=y] ||
> BR2_PACKAGE_KODI_GL [=n]) &&
> BR2_USE_MMU [=y] &&
> BR2_USE_WCHAR [=y] &&
> !BR2_STATIC_LIBS [=n] &&
> BR2_PACKAGE_KODI_ARCH_SUPPORTS [=y] ||
> BR2_PACKAGE_DSTAT [=n] &&
> BR2_USE_WCHAR [=y] &&
> BR2_USE_MMU [=y] &&
> BR2_TOOLCHAIN_HAS_THREADS [=y] &&
> !BR2_STATIC_LIBS [=n] ||
> BR2_PACKAGE_SAMBA4 [=y] &&
> BR2_USE_MMU [=y] &&
> BR2_USE_WCHAR [=y] &&
> BR2_TOOLCHAIN_HAS_NATIVE_RPC [=y] &&
> BR2_TOOLCHAIN_HAS_THREADS [=y] &&
> !BR2_STATIC_LIBS [=n] &&
> !BR2_nios2 [=n] &&
> BR2_TOOLCHAIN_HAS_SYNC_4 [=y]
I guess the && operator has the precedence. So this should be read like:
(BR2_PACKAGE_KODI [=n] && BR2_INSTALL_LIBSTDCPP [=y] &&
BR2_HOST_GCC_AT_LEAST_4_6 [=y] && BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 [=y] &&
BR2_TOOLCHAIN_HAS_THREADS [=y] && !BR2_TOOLCHAIN_USES_MUSL [=n] &&
(BR2_PACKAGE_KODI_EGL_GLES [=y])
||
(BR2_PACKAGE_KODI_GL [=n]) && BR2_USE_MMU [=y] && BR2_USE_WCHAR [=y] &&
!BR2_STATIC_LIBS [=n] && BR2_PACKAGE_KODI_ARCH_SUPPORTS [=y])
||
(BR2_PACKAGE_DSTAT [=n] && BR2_USE_WCHAR [=y] && BR2_USE_MMU [=y] &&
BR2_TOOLCHAIN_HAS_THREADS [=y] && !BR2_STATIC_LIBS [=n])
||
(BR2_PACKAGE_SAMBA4 [=y] && BR2_USE_MMU [=y] && BR2_USE_WCHAR [=y] &&
BR2_TOOLCHAIN_HAS_NATIVE_RPC [=y] && BR2_TOOLCHAIN_HAS_THREADS [=y] &&
!BR2_STATIC_LIBS [=n] && !BR2_nios2 [=n] && BR2_TOOLCHAIN_HAS_SYNC_4[=y])
so it's the last group which selects python2: samba4.
Right now I've deselected it. Then I will try to understand if it can
live with python3.
Best regards
Marco
next prev parent reply other threads:[~2016-05-09 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 20:16 [Buildroot] About python2 and python3 Marco Trapanese
2016-05-09 20:26 ` Thomas Petazzoni
2016-05-09 21:00 ` Marco Trapanese [this message]
2016-05-09 21:16 ` 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=5730FA83.9000608@gmail.com \
--to=marcotrapanese@gmail.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