Hi Pedro, On 09.11.2013 01:58, Pedro Giffuni wrote:
I tried the new --with-system-nss configure option but it failed in the libxmlsec module: ____ .... checking for libxslt libraries >= 1.0.20... no checking for openssl libraries >= 0.9.6... no checking for nspr libraries >= 4.0... no checking for nss libraries >= 3.2... no checking for gnutls libraries >= 0.8.1... no checking for mscrypto libraries... none checking for crypto library... configure: error: At least one crypto library should exist for xmlsec1 yes checking whether byte ordering is bigendian... dmake: Error code 1, while making './unxfbsdx.pro/misc/build/so_configured_so_xmlsec1'
libxmlsec needs the nss development headers and libs. Are they available too?
We could use new checks for configure for that scenario...
[..] But it appears that nspr is not found either:
Maybe the nspr development headers and libs are needed too for building, depending on how the system nss was provided.
While here, I suspect that if libxmlsec could find openssl, it would seriously help progress in the direction of not depending on nss.
That may be an interesting topic after AOO 4.1.
Finally, both openssl and libxmlsec could get an update. libxmlsec is probably not easy to update, but for openssl I uploaded a newer version to apache-extras.
Absolutely. Security critical libraries need to stay up to date.
JIC someone is looking for a good excuse to contribute ;).
Just contribute, no excuses needed ;-) Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
