From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maxime Leroy <maxime@leroys.fr>
Cc: buildroot@buildroot.org, Vincent Jardin <vjardin@free.fr>,
Robin Jarry <robin@jarry.cc>, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v4 2/3] package/grout: new package
Date: Fri, 25 Apr 2025 11:06:51 +0200 [thread overview]
Message-ID: <20250425110651.5a94c78c@windsurf> (raw)
In-Reply-To: <CAHHRULU-eMVN53TCpOxC=rXqOV731eq2iXWn5g0wGUDg-FKJbg@mail.gmail.com>
Hello Maxime,
On Fri, 25 Apr 2025 10:19:12 +0200
Maxime Leroy <maxime@leroys.fr> wrote:
> Grout needs to have UTF-8 local present to run, else it doesn't
> properly start.
Problem is that BR2_ENABLE_LOCALE doesn't tell you an UTF-8 locale is
available. We have no mechanism right now in Buildroot to enforce
having a UTF-8 locale. It could be added separately.
> > + depends on BR2_PACKAGE_DPDK_ARCH_SUPPORTS # dpdk
> > + depends on BR2_TOOLCHAIN_HAS_THREADS # dpdk
> > + depends on BR2_USE_MMU # dpdk, numactl, libecoli, util-linux-smartcols, libcap
> > + depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # dpdk
> > + depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_19 # dpdk
> > + depends on BR2_TOOLCHAIN_USES_GLIBC # dpdk
> > + depends on BR2_TOOLCHAIN_HAS_ATOMIC # numactl
> > + depends on !BR2_STATIC_LIBS # libecoli
> > + depends on BR2_USE_WCHAR # libecoli
>
> Thanks. I am not very familiar about dependencies with buildroot.
> I was planning to change 'select on' to depends on 'DPDK' on a V4 serie.
Using a "depends on" for DPDK could have made sense indeed. But the
other libraries need to be "select"ed, and therefore you anyway need to
inherit their "depends on".
> I thought having a dependencies with DPDK, will be enough to inherit
> of this one.
Nope, that a Kconfig limitation. If you "select" something, you don't
inherit the "depends on" of the thing you select.
> In fact, libcap dependencies was introduced with grout 9.1 released.
> It was not needed for grout 9.0. Thanks for the upgrade.
Ah indeed, that explains it! Thanks for clarifying.
Best regards,
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
next prev parent reply other threads:[~2025-04-25 9:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 11:16 [Buildroot] [PATCH 1/2] package/libecoli: bump version to 0.5.0 Maxime Leroy
2025-03-26 11:16 ` [Buildroot] [PATCH 2/2] package/grout: new package Maxime Leroy
2025-03-26 11:26 ` Vincent Jardin
2025-03-26 12:24 ` Maxime Leroy
2025-03-26 11:21 ` [Buildroot] [PATCH 1/2] package/libecoli: bump version to 0.5.0 Vincent Jardin
2025-03-26 13:26 ` [Buildroot] [PATCH v2 0/2] Add grout package Maxime Leroy
2025-03-26 13:26 ` [Buildroot] [PATCH v2 1/2] package/libecoli: bump version to 0.5.0 Maxime Leroy
2025-03-27 0:23 ` Vincent Jardin
2025-03-26 13:26 ` [Buildroot] [PATCH v2 2/2] package/grout: new package Maxime Leroy
2025-03-27 0:29 ` Vincent Jardin
2025-03-28 8:47 ` [Buildroot] [PATCH v3 0/3] Add grout package Maxime Leroy
2025-03-28 8:47 ` [Buildroot] [PATCH v3 1/3] package/libecoli: bump version to 0.5.0 Maxime Leroy
2025-03-28 8:47 ` [Buildroot] [PATCH v3 2/3] package/grout: new package Maxime Leroy
2025-03-28 8:47 ` [Buildroot] [PATCH v3 3/3] RFC: support/testing: add grout runtime test Maxime Leroy
2025-04-03 15:39 ` [Buildroot] [PATCH v4 0/3] Add grout package Maxime Leroy
2025-04-03 15:39 ` [Buildroot] [PATCH v4 1/3] package/libecoli: bump version to 0.5.0 Maxime Leroy
2025-04-24 21:48 ` Thomas Petazzoni via buildroot
2025-04-03 15:39 ` [Buildroot] [PATCH v4 2/3] package/grout: new package Maxime Leroy
2025-04-24 21:51 ` Thomas Petazzoni via buildroot
2025-04-25 8:19 ` Maxime Leroy
2025-04-25 9:06 ` Thomas Petazzoni via buildroot [this message]
2025-04-25 9:17 ` Thomas Petazzoni via buildroot
2025-04-03 15:39 ` [Buildroot] [PATCH v4 3/3] RFC: support/testing: add grout runtime test Maxime Leroy
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=20250425110651.5a94c78c@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=maxime@leroys.fr \
--cc=robin@jarry.cc \
--cc=thomas.petazzoni@bootlin.com \
--cc=vjardin@free.fr \
/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