[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241121011720.GA69389@pevik>
Date: Thu, 21 Nov 2024 02:17:20 +0100
From: Petr Vorel <pvorel@...e.cz>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-arm-msm@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kbuild@...r.kernel.org, dri-devel@...ts.freedesktop.org,
freedreno@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Rob Clark <robdclark@...il.com>
Subject: Re: [PATCH v4 1/2] init/Kconfig: add python3 availability config
> On Thu, Nov 21, 2024 at 5:41 AM Petr Vorel <pvorel@...e.cz> wrote:
> > It will be used in the next commit for DRM_MSM.
> > Suggested-by: Rob Clark <robdclark@...il.com>
> > Signed-off-by: Petr Vorel <pvorel@...e.cz>
> > ---
> > Changes v3->v4:
> > * Move definition to the end of the file
> I prefer to not check the tool.
Ack.
> Why don't you install python3?
Everybody installs it when it's required, the question is how to inform about
the dependency.
There build environments are minimal environments:
* chroot (e.g. cross compilation)
* container
These are used by both developers and distros.
Kind regards,
Petr
> > init/Kconfig | 3 +++
> > 1 file changed, 3 insertions(+)
> > diff --git a/init/Kconfig b/init/Kconfig
> > index fbd0cb06a50a..c77e45484e81 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -2047,3 +2047,6 @@ config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
> > # <asm/syscall_wrapper.h>.
> > config ARCH_HAS_SYSCALL_WRAPPER
> > def_bool n
> > +
> > +config HAVE_PYTHON3
> > + def_bool $(success,$(PYTHON3) -V)
> > --
> > 2.45.2
Powered by blists - more mailing lists