Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
cannot configure curl 7.71.0 with static WolfSSL installed outside system directories #5605
I did this
On CentOS 7/x86_64...
This works fine on 7.70.0 - just tested successfully to verify. On 7.71.0,
I'm wondering where the bare /wolfssl is coming from and if the new
I expected the following
CentOS 7 (x86_64)
I tested under CentOS 6 (x86_64) as well with the same results.
This appears to be related to the changes in handling WolfSSL with NTLM and interplay with the WolfSSL
Will have to tune my WolfSSL config a bit as I think the issue is there, not curl, but this was unexpected as I've been using something like this for months and multiple curl versions. Thanks!
(we build with wolfSSL outside of system directories in our CI builds, so very frequently...)
Not the OP, but I see the same issue trying to build cURL 7.71.1 with wolfSSL in a Yocto environment.
Quick testing shows that this breaks going from 7.70.0->7.71.0, which would relate it to this commit. It seems like the configure script is trying to take the pkg-config values even if I provide a path to the option.
Configure invoked with:
WolfSSL section of config.log:
The actual part that fails is from the libssh2 tests right after that:
I've confirmed that the commit fixes the config step for my exact case (--with-wolfssl=), but the link for libcurl.so fails with "undefined reference to wolfSSL_DES_ecb_encrypt". This function is hidden behind an extra #ifdef when compared to wolfSSL_DES_set_odd_parity that is tested for in the configure script when checking to add NTLM support (at least in the two versions of wolfSSL I have access to - 4.3 and 4.4). This function (for whatever reason) only gets added to the OpenSSL compatibility layer if the user is building for stunnel, wpa_supplicant, or openVPN support - otherwise it is not present.
Using the plain "--with-wolfssl" fails a Yocto QA check, because the addcflag, etc, doesn't get blanked back to defaults properly.
I've got a pretty good idea of what to do to fix all this, so I'll be sending a PR in soon.