From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Ford <aford173@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libxml-parser-perl: add host-libxcrypt dependency
Date: Mon, 24 Aug 2026 19:15:58 +0200 [thread overview]
Message-ID: <aox73MQnOLsOq-tt@windsurf> (raw)
In-Reply-To: <20260716133001.2147463-1-aford173@gmail.com>
Hello,
On Thu, Jul 16, 2026 at 08:30:01AM -0500, Adam Ford wrote:
> host-libxml-parser-perl compiles XS modules against the system perl
> headers, which #include <crypt.h>. On build hosts without libcrypt-dev
> installed, the build fails:
>
> .../CORE/reentr.h:126:16: fatal error: crypt.h: No such file or directory
>
> Declaring host-libxcrypt ensures crypt.h is present in the per-package
> host sysroot before the build.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Sorry for the delay in getting back to you. Could you provide some
details on the environment/distribution where crypt.h is not available
on the host? I've tried but on Fedora or Ubuntu, as soon as
glibc-devel (or equivalent) is installed, it pulls in
libxcrypt-devel. On Archlinux, /usr/include/crypt.h is also present.
Thanks for the additional information that you'll provide on this
topic!
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:[~2026-08-24 17: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 [this message]
2026-08-24 18:12 ` Nicolas Cavallari
2026-08-24 19:16 ` Thomas Petazzoni via buildroot
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=aox73MQnOLsOq-tt@windsurf \
--to=buildroot@buildroot.org \
--cc=aford173@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