Pierre Pronchery 1a18383a52 libcrypto: link engines and the legacy provider to libcrypto ... OpenSSL's legacy provider module and engines need to link to libcrypto.so, as it provides some of the actual implementations of legacy routines. This is a little tricky due to build order issues. Introduce a small hack (LIBCRYPTO_WITHOUT_SUBDIRS) that builds libcrypto.so in its usual early phase without any OpenSSL provider modules or engines. This is intended to restore the test suite; a future change should remove the hack and replace it with a better approach. PR: 254853, 273528 Discussed with: Folks at EuroBSDCon in Coimbra Sponsored by: The FreeBSD Foundation		2023-09-16 16:55:12 +01:00
..
engines	libcrypto: link engines and the legacy provider to libcrypto	2023-09-16 16:55:12 +01:00
man	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
modules	libcrypto: link engines and the legacy provider to libcrypto	2023-09-16 16:55:12 +01:00
libcrypto.pc.in	Merge OpenSSL 3.0.9	2023-06-23 18:53:36 -04:00
Makefile	libcrypto: link engines and the legacy provider to libcrypto	2023-09-16 16:55:12 +01:00
Makefile.asm	libcrypto: Refactor Makefile.asm so it can be run outside of buildenv	2023-08-29 14:39:36 -07:00
Makefile.common	libcrypto: Add buildasm and cleanasm targets	2023-08-29 14:43:51 -07:00
Makefile.depend	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
Makefile.inc	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
Makefile.man	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
Version.map	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00