Re: Issue with Apache HTTP Server Build: Legacy libcrypt.so.1 Dependency on RHEL 10

"Rathore, Rajendra" <[email protected]> Fri, 25 Jul 2025 14:26:41 +0000
Newsgroups gmane.comp.apache.user
Message-ID <BY3PR17MB5395F0323D0AD8F587B904C2B659A@BY3PR17MB5395.namprd17.prod.outlook.com>
Hi Eric,

As I am new to build apache and all, can you elaborate more on how to build APR without linking to that library, as we are bundling APR also.

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Eric Covener <[email protected]>
Sent: Friday, July 25, 2025 6:54 PM
To: [email protected] <[email protected]>
Subject: Re: [users@httpd] Issue with Apache HTTP Server Build: Legacy libcrypt.so.1 Dependency on RHEL 10

On Fri, Jul 25, 2025 at 9:17 AM Rathore, Rajendra
<[email protected]> wrote:
>
> Hi Team,
>
> We are currently bundling the Apache HTTP Server from source on a Linux machine(RHEL 7.x/ RHEL 8.x). During the build process, we are passing a custom OpenSSL path using the --with-ssl configuration flag. However, the final build still includes a dependency on the legacy libcrypt.so.1 library.

note that the issue is libcrypt, not libcrypto, which is about
password validation in APR and not SSL.

The symbols removed in libcrypt 2.x seem to be super obscure things.
It's a shame libcrypr.so.1 wasn't left with a semver break.

I opened a redhat ticket on this about the removal in RHEL 10 and got nowhere.
In my own object-code-only (1 per arch, not distro) products I hack
around this in APR builds by avoiding linking with it and poking
around with dlopen.

You might want to push RedHat for some toleration here.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]