openssl/Configure, branch openssl-3.2

Copyright year updates

2025-07-01T12:04:53Z

Reviewed-by: Matt Caswell Reviewed-by: Neil Horman Release: yes

Disable unterminated-string-initialization in strict-warnings

2025-05-02T11:43:39Z

Recently updated to fedora 42, which includes an updated gcc, which triggers a new warning: test/afalgtest.c:44:9: error: initializer-string for array of 'unsigned char' truncates NUL terminator but destination lacks 'nonstring' attribute (18 chars into 17 available) [-Werror=unterminated-string-initialization] 44 | "\x53\x69\x6e\x67\x6c\x65\x20\x62\x6c\x6f\x63\x6b\x20\x6d\x73\x67" The warning occurs because in some locations we create char buffers of length X, and fill it with X bytes of data, truncating the NULL terminator. We could fix it by adding the nonstring attribute, but given that: 1) Adding attributes might impact other platforms that don't understand the attribute. 2) We often create char buffers that don't expect a NULL terminator. 3) Converting the unsigned char arrays to uint8_t, or other types that could be interpreted as non-strings has no impact, only applying the nonstring attribute silences the warning. It seems more sensible to just disable the warning entirely Reviewed-by: Saša Nedvědický Reviewed-by: Richard Levitte Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/27490) (cherry picked from commit d08d77789e20e8b47a48f4d0a998ccfcde9d389b)

Configure: Remove -Wswitch-default from strict warnings

2024-07-03T09:26:43Z

Also move -Wno-tautological-constant-out-of-range-compare to clang-specific options as it is not supported by gcc. Reviewed-by: Bernd Edlinger Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/24758) (cherry picked from commit 3d9c6b16d8b8e75b73e2fd34849e930e2792f3a4)

Add aix-clang and aix64-clang configuration

2024-06-28T13:20:51Z

Reviewed-by: Neil Horman Reviewed-by: Tom Cosgrove Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/24609) (cherry picked from commit 7afa7731e924d5ac10fc992d8cd777f407d33af9)

Configure: make absolutedir() use rel2abs() on Windows too

2024-06-15T12:14:48Z

perl's realpath() seems to be buggy on Windows, so we turn to rel2abs() there as well. Fixes #23593 Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/24569) (cherry picked from commit 6e01d3114b77c82cf83a2bfe53f7ba97840fbe36)

Copyright year updates

2024-06-04T12:58:30Z

Reviewed-by: Neil Horman Release: yes

Add atexit configuration option to using atexit() in libcrypto at build-time.

2024-02-22T09:35:32Z

This fixes an issue with a mix of atexit() usage in DLL and statically linked libcrypto that came out in the test suite on NonStop, which has slightly different DLL unload processing semantics compared to Linux. The change allows a build configuration to select whether to register OPENSSL_cleanup() with atexit() or not, so avoid situations where atexit() registration causes SIGSEGV. INSTALL.md and CHANGES.md have been modified to include and describe this option. Signed-off-by: Randall S. Becker Signed-off-by: Tomas Mraz Reviewed-by: Tom Cosgrove Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/23642)

Configure: Fix ordering bug when processing split DEPENDs

2024-02-08T10:39:29Z

Configure was recently made to process this sort of line: DEPEND[generated]=util/perl|OpenSSL/something.pm Unfortunately, in processing such lines, the order in which paths were recomputed caused some resulting paths to be faulty under some circumstances. This change fixes that. Fixes #22853 Reviewed-by: Tom Cosgrove Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/23500)

Configure: Refuse to make directories in the source tree

2023-12-07T06:54:53Z

Fixes #22907 Reviewed-by: Tomas Mraz Reviewed-by: Todd Short (Merged from https://github.com/openssl/openssl/pull/22908) (cherry picked from commit 504ff2a4ef5f26990a48ca3d664ac1e5d9cb20b9)

Configure: do not check for an absolute prefix in cross-builds

2023-11-15T10:11:00Z

The check is always made according to the host platform's rules, which may not be true for true when the target platform is different, e.g. when cross-building for Windows on a Linux machine. So skip this check when used together with the `--cross-compile-prefix=` option. Fixes https://github.com/openssl/openssl/issues/9520 Reviewed-by: Paul Dale Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/22723) (cherry picked from commit 4ea752997df83c2a694fdb157aab07908303fc90)