Thanks, that was helpful. It turns out that it had nothing to do with openssl. The error in the log had to do with xalan-c not being found. I had forgotten that when I build xalan-c that it is creating libraries in a lib64 directory now instead of just lib. This is the first time I have used cmake to build xalan-c and the output directories generated are slightly different than they had been in the past. The error message printed to the console indicated that it couldn't find libcrypto. It was trying to do a link command to find libcrypto using a build command that would also attempt to link against all of the dependencies so the error in the configuration log didn't match what was printed to the console.
Thanks, Shawn Fox -----Original Message----- From: Cantor, Scott <[email protected]> Sent: Wednesday, November 1, 2023 8:47 AM To: [email protected] Subject: Re: Apache Santuario config states that libcrypto is not found External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. > I'm confused by the purpose of specifying the location of the openssl > that I have built if the dependency mechanism is searching for > libcrypt somewhere else. Because it found a pkgconfig from OpenSSL somewhere else and it told it something you don't want to use. That's the point of the mechanism, pkgconfig takes care of all the flags and filenames, as long as the build knows which pkgconfig file to use. -- Scott
