Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fred Lefranc <fred.lefranc.evs@gmail.com>
Cc: Fred Lefranc <fred.lefranc+evs@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] package/busybox: fix build with glibc 2.39
Date: Wed, 17 Jul 2024 16:58:41 +0200	[thread overview]
Message-ID: <20240717165841.4b643240@windsurf> (raw)
In-Reply-To: <20240717121147.1353901-1-fred.lefranc+evs@gmail.com>

On Wed, 17 Jul 2024 14:11:46 +0200
Fred Lefranc <fred.lefranc.evs@gmail.com> wrote:

> When glibc was bumped to version 2.39 in commit b5680f53d60acf8ff6010082f873438a39bd5d97,
> it removed the deprecated libcrypt support.
> 
> In such a situation, until the upgrade of glibc to 2.39, Busybox could rely on the
> libcrypt provided by glibc. Since version 2.39, glibc no longer provides libcrypt,
> causing a build failure with Busybox configurations that have CONFIG_USE_BB_CRYPT
> disabled.
> 
> To fix this, add the libxcrypt dependency to Busybox when BR2_PACKAGE_LIBXCRYPT is
> selected. The user is still responsible for enabling BR2_PACKAGE_LIBXCRYPT when
> their Busybox configuration has CONFIG_USE_BB_CRYPT disabled.
> 
> Signed-off-by: Fred Lefranc <fred.lefranc+evs@gmail.com>
> ---
> Changes v3 -> v4
>   - fix commit message to explain the non-working case
> Changes v2 -> v3
>   - fix commit message
> Changes v1 -> v2
>   - busybox.mk: fix BUSYBOX_DEPENDENCIES ident & remove the check
> for BR2_TOOLCHAIN_USES_GLIBC (req by Thomas)
>   - Config.in: remove libxcrypt mandatory dependency
> (req by Thomas)
> ---
>  package/busybox/busybox.mk | 4 ++++
>  1 file changed, 4 insertions(+)

Thanks for your persistence, patch applied! The lines of the commit log
were a bit too long, so I rewrapped the paragraphs.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-17 14:58 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
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 [this message]
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=20240717165841.4b643240@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fred.lefranc+evs@gmail.com \
    --cc=fred.lefranc.evs@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox