possible to link libressl in place of openssl in MACOS compile points #25916

As you can see the question is ? in the title. I have exhausted trying to brew install openssl@3 and brew install openssl and brew link openssl after download after all prerequisites except qt, no GUI in this build... then ./autogen.sh and then ./configure and i get this far / as shown below no cigar... avail.

bash-3.2$ ./configure
checking build system type... x86_64-apple-darwin17.7.0
checking host system type... x86_64-apple-darwin17.7.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... ./build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 

###... and...######### ###a lot of output#### ###...cont'd...#######

checking for Berkeley DB C++ headers... default
checking for main in -ldb_cxx-4.8... yes
checking for miniupnpc/miniwget.h... yes
checking for upnpDiscover in -lminiupnpc... yes
checking for miniupnpc/miniupnpc.h... yes
checking for upnpDiscover in -lminiupnpc... (cached) yes
checking for miniupnpc/upnpcommands.h... yes
checking for upnpDiscover in -lminiupnpc... (cached) yes
checking for miniupnpc/upnperrors.h... yes
checking for upnpDiscover in -lminiupnpc... (cached) yes
checking for Qt5Core Qt5Gui Qt5Network Qt5Widgets... no
configure: WARNING: Qt dependencies not found; bitcoin-qt frontend will not be built
checking whether to build Bitcoin Core GUI... no (Qt5)
checking for boostlib >= 1.47.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
checking for mismatched boost c++11 scoped enums... ok
checking for libssl... no
configure: error: openssl not found.

OpenSSL is not required to compile any recent version of Bitcoin Core. What version are you trying to compile.

Which version of Mac OS are you using could you provide more details regarding that.

Closing for now. The last version to require OpenSSL was 0.19.x. That went EOL in August of 2021. I'd suggest trying to compile a newer version of Bitcoin Core.

10.13

I have tried what yall asked me to do, which is start over. and i keep failing right here...

checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking whether make supports the include directive... yes (GNU style)
checking dependency style of g++... gcc3
checking whether g++ supports C++17 features with -std=c++17... yes
checking whether std::filesystem can be used without link library... no
checking whether std::filesystem needs -lstdc++fs... no
checking whether std::filesystem needs -lc++fs... configure: error: in `/Users/folderhub/bitcoin':
configure: error: cannot figure out how to use std::filesystem
See `config.log' for more details

There is nothing we can do here. You will need to see the `config.log' for more details, as the prompt told you to. Otherwise, we'll need exact steps to reproduce with the compiler you used, including the compiler version.