This makes it annoying to distribute binaries (when not cross compiling).
To distribute perl binaries, you have to ensure it does not link to glibc's libcrypt, since that may not exist on other systems, so it's best to build libxcrypt and distribute together...
But to configure libxcrypt, you need perl 5.14 with open.pm, which is not available on RHEL and derivatives by default, and you may not have access to yum install perl-open.
So without root access, you have to bootstrap a minimal perl yourself to configure libxcrypt, so you can build perl with crypt support.
The latter is not satisfactory cause it's overly complex, and the bootstrap perl won't be a deterministic build (it may or may not link against glibcs libcrypt), and cannot be distributed itself.
Would it be possible to drop the build dependency on perl in favor of something that does not depend on libcrypt?
libxcrypthas a build dependency onperlperllinks tolibcryptThis makes it annoying to distribute binaries (when not cross compiling).
To distribute perl binaries, you have to ensure it does not link to
glibc's libcrypt, since that may not exist on other systems, so it's best to buildlibxcryptand distribute together...But to configure
libxcrypt, you needperl5.14 withopen.pm, which is not available on RHEL and derivatives by default, and you may not have access toyum install perl-open.So without root access, you have to bootstrap a minimal
perlyourself to configurelibxcrypt, so you can buildperlwith crypt support.The latter is not satisfactory cause it's overly complex, and the bootstrap perl won't be a deterministic build (it may or may not link against glibcs libcrypt), and cannot be distributed itself.
Would it be possible to drop the build dependency on perl in favor of something that does not depend on libcrypt?