Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi guys,

        I got the appended (transient I hope) failure of the build in xmlsec.

        Is it possible that we're missing a dependency on openssl / nss in
there ? [ it -looks- to my uneducated eye ] as if we have only a libxml2
dependency.

        HTH,

                Michael.

...
checking for __FUNCTION__ or __func__... __FUNCTION__
checking size of size_t... 4
checking for xml2-config... /usr/bin/xml2-config
checking libxml2 /usr/bin/xml2-config ... yes ('2.7.8')
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
make[1]: ***
[/data/opt/libreoffice/master/workdir/unxlngi6.pro/ExternalProject/xmlsec/build] Error 1
make[1]: *** Waiting for unfinished jobs....

-----------------------------------------------------------------------
        Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
            http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 512 occurred while
making /data/opt/libreoffice/master/tail_build/prj

 it seems that the error is inside 'tail_build', please re-run build
 inside this module to isolate the error and/or test your fix.


-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.