On August 21, 2021 5:35 AM, Daniel Stenberg wrote: >On Fri, 20 Aug 2021, Randall S. Becker via curl-library wrote: > >> My latest configure command for OpenSSL 3.0 is: >> >> CFLAGS="-c99" CPPFLAGS="-D_XOPEN_SOURCE_EXTENDED=1 -Wlp64 -WIEEE_float >> -I/usr/local-ssl3.0/openssl/include" LDFLAGS="-L/usr/local-ssl3.0/lib" >> conf_script_floss_cc --with-ssl=/usr/local-ssl3.0 --disable-pthreads >> --disable-threaded-resolver --enable-ipv6' > >On 64 bit systems, OpenSSL doesn't make a 'lib' anymore. It uses lib64 only >(and no, I don't know why they decided this). My custom >OpenSSL 3 install dir: > >$ ls ~/build-openssl/ >bin include lib64 share ssl > >This breaks old curl configure scripts but the current one is adapted and I >build with OpenSSL 3 fine and we have a CI job doing it as well. > >My configure line for this needs nothing special: > > ./configure --with-ssl=$HOME/build-openssl > >... even if I also usually set LDFLAGS="-Wl,-rpath,$HOME/build-openssl/lib64" >to make it co-exist with other OpenSSL installs better.
I don't see the same thing - and there is no lib64 directory in OpenSSL 3 anywhere. Using OpenSSL 3.0.0 beta2, my directory is as follows: /usr/local-ssl3.0: ls lib engines-3 libcrypto.so libssl.so pkgconfig libcrypto.a libssl.a ossl-modules The OpenSSL build is definitely 64 bit - I know because I did the build/install about 2 weeks ago. If I leave off the -Wlp64, the linker complains about mixing 64 (openssl) and 32 models (curl) during the configure phase claiming it can't find openssl. This is really perplexing. Randall ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
