From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Peter Seiderer <ps.report@gmx.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ntpsec: depends on python3
Date: Sat, 23 Jul 2022 22:25:10 +0200 [thread overview]
Message-ID: <20220723222510.3eb766d3@windsurf> (raw)
In-Reply-To: <20220723212807.4912-1-fontaine.fabrice@gmail.com>
On Sat, 23 Jul 2022 23:28:07 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Depends on python3 instead of selecting it to avoid the following build
> failure raised since the addition of the package in commit
> 27b8d0ba8c4004819e092fb81c0f64f284b3aa4a:
>
> Makefile:576: *** libffi is in the dependency chain of python3 that has added it to its _DEPENDENCIES variable without selecting it or depending on it from Config.in. Stop.
>
> Fixes:
> - http://autobuild.buildroot.org/results/2893c213f49d37a0878dcf14ec68ef991471c70f
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Gaah, my bad, I forgot to propagate the dependencies of python3.
The correct fix is:
depends on BR2_USE_MMU # python3
depends on BR2_TOOLCHAIN_HAS_THREADS # python3
depends on !BR2_STATIC_LIBS # python3
select BR2_PACKAGE_PYTHON3
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-23 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 21:28 [Buildroot] [PATCH 1/1] package/ntpsec: depends on python3 Fabrice Fontaine
2022-07-23 20:25 ` Thomas Petazzoni via buildroot [this message]
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=20220723222510.3eb766d3@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
/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.