From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/crun: fix musl and uclibc-ng builds
Date: Sun, 6 Nov 2022 14:58:59 +0100 [thread overview]
Message-ID: <20221106135859.GR3918838@scaer> (raw)
In-Reply-To: <20221106105309.350587-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2022-11-06 11:53 +0100, Fabrice Fontaine spake thusly:
> Fix the following musl and uclibc-ng build failures raised since the
> addition of the package in commit
> 530d6f661e506a4774b7236cb93d65f669adbc92:
>
> configure: error: *** argp functions not found - install libargp or argp_standalone
>
> Fixes:
> - http://autobuild.buildroot.org/results/55b283fa46a797253193fb752638ba88597a416b
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/crun/Config.in | 1 +
> package/crun/crun.mk | 4 ++++
> 2 files changed, 5 insertions(+)
>
> diff --git a/package/crun/Config.in b/package/crun/Config.in
> index 5aca10dcdb..5def7001c1 100644
> --- a/package/crun/Config.in
> +++ b/package/crun/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_CRUN
> bool "crun"
> + select BR2_PACKAGE_ARGP_STANDALONE if BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_MUSL
I find it a bit weirs that the select uses the uclibc||musl construct,
but that argp-standalone depends on !glibc.
Yes, the two conditions are technical equivalent, but still it is weird.
I looked at what we currently have, and it turns out that we have only
one case where the select uses !glibc (xen), 12 where we use
ublibc||musl, and 1 only uclibc (elfutils, which is glibc or uclibc
only).
so... Applied to master as-is, thanks.
Regards,
Yann E. MORIN.
> select BR2_PACKAGE_YAJL # libocispec
> help
> crun is a fast and low-memory OCI Container Runtime in C.
> diff --git a/package/crun/crun.mk b/package/crun/crun.mk
> index 4a0c150594..65f166e657 100644
> --- a/package/crun/crun.mk
> +++ b/package/crun/crun.mk
> @@ -15,6 +15,10 @@ CRUN_CPE_ID_VENDOR = crun_project
> CRUN_AUTORECONF = YES
> CRUN_CONF_OPTS = --disable-embedded-yajl
>
> +ifeq ($(BR2_PACKAGE_ARGP_STANDALONE),y)
> +CRUN_DEPENDENCIES += argp-standalone
> +endif
> +
> ifeq ($(BR2_PACKAGE_LIBCAP),y)
> CRUN_DEPENDENCIES += libcap
> CRUN_CONF_OPTS += --enable-caps
> --
> 2.35.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-06 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 10:53 [Buildroot] [PATCH 1/1] package/crun: fix musl and uclibc-ng builds Fabrice Fontaine
2022-11-06 13:58 ` Yann E. MORIN [this message]
2022-11-06 18:03 ` Christian Stewart via buildroot
2022-11-06 18:55 ` Yann E. MORIN
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=20221106135859.GR3918838@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox