From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fred Lefranc <fred.lefranc.evs@gmail.com>
Cc: Fred Lefranc <fred.lefranc+evs@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/busybox: fix build with glibc 2.39
Date: Mon, 15 Jul 2024 12:31:53 +0200 [thread overview]
Message-ID: <20240715123153.014a936f@windsurf> (raw)
In-Reply-To: <20240715101607.1288233-1-fred.lefranc+evs@gmail.com>
Hello Fred,
On Mon, 15 Jul 2024 12:16:06 +0200
Fred Lefranc <fred.lefranc.evs@gmail.com> wrote:
> diff --git a/package/busybox/Config.in b/package/busybox/Config.in
> index 3c2aa515f8..85fa0c7f9a 100644
> --- a/package/busybox/Config.in
> +++ b/package/busybox/Config.in
> @@ -1,6 +1,7 @@
> config BR2_PACKAGE_BUSYBOX
> bool "BusyBox"
> default y
> + select BR2_PACKAGE_LIBXCRYPT if BR2_TOOLCHAIN_USES_GLIBC
I'm not sure we want to make this a mandatory dependency. Indeed, with
our default Busybox configuration it's not needed.
> +ifeq ($(BR2_PACKAGE_LIBXCRYPT)$(BR2_TOOLCHAIN_USES_GLIBC),yy)
> + BUSYBOX_DEPENDENCIES += libxcrypt
No indentation for BUSYBOX_DEPENDENCIES.
> +endif
So basically, I would just do:
ifeq ($(BR2_PACKAGE_LIBXCRYPT),y)
BUSYBOX_DEPENDENCIES += libxcrypt
endif
and leave it up to the users who tweak their Busybox configuration to
figure out that they need to enable BR2_PACKAGE_LIBXCRYPT.
I remember there was some discussion with Yann on IRC about this topic,
but I don't remember what the conclusion was, but the above would be my
suggestion.
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:[~2024-07-15 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 10:16 [Buildroot] [PATCH] package/busybox: fix build with glibc 2.39 Fred Lefranc
2024-07-15 10:31 ` Thomas Petazzoni via buildroot [this message]
2024-07-15 11:10 ` [Buildroot] [PATCH v2] " Fred Lefranc
2024-07-15 14:08 ` Thomas Petazzoni via buildroot
2024-07-15 14:54 ` Fred Lefranc
2024-07-16 7:59 ` [Buildroot] [PATCH v3] " Fred Lefranc
2024-07-16 14:23 ` Thomas Petazzoni via buildroot
2024-07-16 17:32 ` Fred Lefranc
2024-07-16 19:39 ` Thomas Petazzoni via buildroot
2024-07-17 12:11 ` [Buildroot] [PATCH v4] " Fred Lefranc
2024-07-17 14:58 ` Thomas Petazzoni via buildroot
2024-07-17 15:52 ` Fred Lefranc
2024-08-28 8:49 ` Peter Korsgaard
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=20240715123153.014a936f@windsurf \
--to=buildroot@buildroot.org \
--cc=fred.lefranc+evs@gmail.com \
--cc=fred.lefranc.evs@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@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