From ed3b4926895338a2067939631318b7734162808f Mon Sep 17 00:00:00 2001 From: Michael Graeb Date: Fri, 23 Aug 2024 01:19:47 +0000 Subject: [PATCH] move libcrypto weirdness to aws-c-cal's CMakeLists.txt --- cmake/AwsCFlags.cmake | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/cmake/AwsCFlags.cmake b/cmake/AwsCFlags.cmake index c800aa7ff..8e752d2e4 100644 --- a/cmake/AwsCFlags.cmake +++ b/cmake/AwsCFlags.cmake @@ -159,18 +159,6 @@ function(aws_set_common_properties target) # This becomes a define in config.h set(AWS_HAVE_POSIX_LARGE_FILE_SUPPORT ${HAS_LFS} CACHE BOOL "Posix Large File Support") - # Hide symbols from libcrypto.a - # This avoids problems when an application ends up using both libcrypto.a and libcrypto.so. - # - # An example of this happening is the aws-c-io tests. - # All the C libs are compiled statically, but then a PKCS#11 library is - # loaded at runtime which happens to use libcrypto.so from OpenSSL. - # If the symbols from libcrypto.a aren't hidden, then SOME function calls use the libcrypto.a implementation - # and SOME function calls use the libcrypto.so implementation, and this mismatch leads to weird crashes. - if (UNIX AND NOT APPLE) - target_link_options(${target} PUBLIC "LINKER:--exclude-libs,libcrypto.a") - endif() - endif() check_include_file(stdint.h HAS_STDINT)