Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Cc: Adam Ford <aford173@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libxml-parser-perl: add host-libxcrypt dependency
Date: Mon, 24 Aug 2026 21:16:14 +0200	[thread overview]
Message-ID: <aoyYXMGZuloqjM-z@windsurf> (raw)
In-Reply-To: <e18f7c88-3d2a-4ca1-9c5d-9522cb76cc2f@green-communications.fr>

Hello Nicolas,

On Mon, Aug 24, 2026 at 08:12:52PM +0200, Nicolas Cavallari wrote:
> Not the author but in Debian Forky (testing) and Sid, libc6-dev no longer
> depends on libcrypt-dev, the provider of crypt.h.  libcrypt-dev now only
> have these reverse dependencies:
> 
> gauche-dev, guile-3.0-dev, heimdal-multidev, libapr1-dev,
> libidzebra-2.0-dev, libperl-dev, libuser1-dev, sa-compile
> 
> None of which would be typically present on a developer or builder system.

Thanks for this additional information! With this, I was able to
reproduce the build issue, so I applied the patch to our master
branch.

Thanks a lot!

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:[~2026-08-24 19:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 13:30 [Buildroot] [PATCH] package/libxml-parser-perl: add host-libxcrypt dependency Adam Ford
2026-07-31 21:04 ` Adam Ford
2026-08-24 17:15 ` Thomas Petazzoni via buildroot
2026-08-24 18:12   ` Nicolas Cavallari
2026-08-24 19:16     ` Thomas Petazzoni via buildroot [this message]
2026-08-24 19:15 ` Thomas Petazzoni via buildroot
2026-09-04 12:18 ` Thomas Perale via buildroot

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=aoyYXMGZuloqjM-z@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aford173@gmail.com \
    --cc=nicolas.cavallari@green-communications.fr \
    --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