Re: [Buildroot] Analysis of host-libxcrypt build failures

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

On Tue, 31 Dec 2024 17:12:49 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> The obvious thing to fix is to get the perl executable to have a proper
> RPATH of course.

I have sent a patch doing just this:

  https://patchwork.ozlabs.org/project/buildroot/patch/20250101202112.1845113-1-thomas.petazzoni@bootlin.com/

> However, this means in the scenario above that perl will be
> built/linked against the system libcrypt.so, and then after
> host-libxcrypt is built/installed, host/bin/perl will from this point
> on run with libcrypt.so in host/lib, which isn't really ideal. Should
> we make host-libxcrypt a mandatory dependency of host-perl? How do we
> detect this situation in other packages? Should check-host-rpath have
> instead a allow-list of libraries (libc, libm) for which we accept to
> use the system-provided ones, and for everything else (including
> libcrypt), we expect HOST_DIR/lib to provide them?
> 
> For the record, we have host-libxcrypt because host-systemd was failing
> to build on systems that have a recent glibc installed, but don't have
> libxcrypt installed system-wide.

I wanted to test building host-perl on a system with libxcrypt
installed, but I wasn't able to easily find a Docker container of a
distro that doesn't have libxcrypt installed by default.

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