I don't think you are missing anything -- configure just assumes that the old API is available.
Hopefully the code itself doesn't depend on the old API, so maybe you can replace that check in configure with something else? E.g. ERR_get_error() __Martin >>>>> On Mon, 1 Jun 2020 08:53:01 +0200, Philip Brown said: > > Hello Baculistas, > > I see from the 9.0.6 release notes it is said that Bacula can now be > built with openSSL-1.1.1. > > I have been building bacula 9.6.3 for omnios which comes with > openssl-1.0.2 and 1.1.1 (with --api=1.0.0) but could not get the TLS > parts working. I built my own version of openssl-1.1.1 with --api=0.9.8 > and everything (TLS & Client Data Encryption) functions correctly. > > Under openssl-1.0.2/1.1.1 (with --api=1.0.0), "./configure" tests for > openssl by making a call to "CRYPTO_set_id_callback", which is not > available/deprecated from 1.0.0 on-wards. So "./configure" will complete > without TLS or Encryption support. > > What I wanted to ask here, is, am I missing something? Is there away > around having to build openssl-1.1.1 with --api=0.9.8? Is there a > compile time option in Bacula to allow the 0.9.8 calls? > > Thanks, > Philip _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
