Looking at testcrypto.c, this never worked, not on Linux or Windows or anywhere, so it's not a regression. It's an all-or-nothing review of both schemas indiscriminately, whenever APU_HAVE_CRYPTO is defined. It ignores the presence of NSS vs OPENSSL.
We didn't do this with the many other multiple-provider schemas, I guess this is just special? In any case, it's an alert but not critical, unless you attempted to build both crypto providers. On Wed, Oct 18, 2017 at 3:39 PM, Michal Karm <michal.baba...@gmail.com> wrote: > Hi guys, > > I've switched my Windows CI from APR Util 1.5.x > to the 1.6.x branch. Little did I know it would > demand NSS even though I built with OpenSSL. > > This is the pertinent excerpt from the log [1], > the full build log (large text) can be found here [2] > and last but not least, this is the build script [3], > note that I tried to set -DAPU_HAVE_NSS=OFF out of good > sport, but it was in vain. > > Could you tell me what might be improved in the > CMakeLists.txt so as the test run doesn't look for NSS? > > Is there anything else fishy about it? Perhaps the root > cause is entirely different. > > Thank you for any pointers > > > Cheers > > Karm > > [1] https://www.hastebin.com/umitizokor.lua > [2] https://ci.modcluster.io/job/apr-util-windows/15/label=w2k12r2/consoleText > [3] > https://github.com/modcluster/ci.modcluster.io/blob/6a01bf9f015224271078336eebab4e258b8f9196/windows/apr-util/build.bat#L28 > > Michal Karm Babacek > > -- > Sent from my Hosaka Ono-Sendai Cyberspace 7 > >
