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 v2] package/busybox: fix build with glibc 2.39
Date: Mon, 15 Jul 2024 16:08:09 +0200	[thread overview]
Message-ID: <20240715160809.351cdc89@windsurf> (raw)
In-Reply-To: <20240715111003.1296141-1-fred.lefranc+evs@gmail.com>

Hello Fred,

On Mon, 15 Jul 2024 13:10:02 +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.
> 
> As glibc's libcrypt was providing systemd's libcrypt dependency this
> broke any systemd build using glibc version 2.39.
> 
> To fix this add the libxcrypt dependency to busybox which is the
> preferred way of providing libcrypt support in busybox as the glibc
> variant is only used as a fallback due to being deprecated.

I'm sorry but I don't follow you on this last paragraph, in particular
the part "as the glibc variant is only used as a fallback due to being
deprecated".

What happens is that recent glibc versions no longer provide libcrypt,
so libxcrypt should be used as a replacement. And it's up to the user
to enable BR2_PACKAGE_LIBXCRYPT if the user enables an applet in the
Busybox configuration that needs lib(x)crypt features.

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

  reply	other threads:[~2024-07-15 14:08 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 [this message]
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=20240715160809.351cdc89@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