Adding --libdir=lib to config or Configure should work. Haven't tried
though.
Am 23.08.2021 um 11:15 schrieb Rainer Jung:
In my environment I used a lame workaround, moved the private OpenSSL
installation lib64 directory to lib and symlinked lib64 to lib. But let
me check, whether I find a hook in OpenSSL building that brings back the
old lib directly....
Regards,
Rainer
Am 23.08.2021 um 10:56 schrieb Mark Thomas:
On 23/08/2021 09:45, Rainer Jung wrote:
I noticed the same - switch from lib to lib64 as the default library
installation directory - when I recently built OpenSSL 3.0.0 beta2.
It must be a change during the last 1-2 months between alpha16 and
beta2).
Thanks for the confirmation.
How do you recommend we handle this? I know Gump is affected and I
suspect Tomcat Native will be as well. I'd like to be able to build
with OpenSSL 3.0.0 or 1.1.1 with minimal changes.
Should we try and change OpenSSL to use /lib or the dependent builds
to look in /lib64 (or ideally /lib and /lib64 so either works). And
how to do that?
Thanks,
Mark
Regards,
Rainer
Am 23.08.2021 um 10:35 schrieb Mark Thomas:
Hi,
I've noticed that both local and Gump builds of OpenSSL master have
started using .../lib64 rather than .../lib for the shared libraries
that are built. This is causing build problems - for example httpd
looks in /lib
I'm not sure if something has changed in the build environments or
in openssl.
Any idea a) what might have triggered this and b) the best way to
handle it so the builds work?
Thanks,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
