GNOME Bugzilla – Bug 774181
3.22: NSS and NSPR should be required independently and unconditionally
Last modified: 2016-11-27 20:46:26 UTC
The logic in configure.ac checking for NSPR and NSS is not quite right - it fails if you have NSPR installed from pkg-config and NSS flags specified manually, for example. This should clean it up a bit, and do the checks independently and unconditionally.
Created attachment 339436 [details] [review] build: Check for NSS and NSPR independently NSS and NSPR are required even if --disable-smime is given, so check for them independently of each other and of the SMIME option.
Thanks for a bug report and patch, but I'm not going to change such fundamental thing in the stable release. The development version doesn't use autotools, it uses CMake, thus your patch is not going to be committed.
OK, I'm trying to create a stable JHBuild setup for 3.22 on macOS, I'll see if I can get it to work with the NSS and NSPR that I'm currently building (I had several different configurations over the past few days). Otherwise I'll have to use a tarball of e-d-s with my patch applied.
Right, that's the only option for the stable branch. If you'd have anything for CMake (git master branch), then feel free to share it, just note that as it is now it's either both or nothing (NSS & NSPR) in the code, which reflects the way it is looked for it in the configure itself. You still can build with -DENABLE_SMIME=OFF, which is intentional.
I didn't save my build logs unfortunately, but it seems that NSS and NSPR are still required by parts of Camel even if building without SMIME. I'm not sure if _that_ was intentional, but I assumed it was. In any case, I fixed this problem in a different way.