Or maybe I could build the patched xmlsec1 component out of the LO fetched tarball, as a system library (naming it as LO version), then force the LO build not to build that component? Da: Gabriele Bulfon A: Rene Engelhard Cc: michael.me...@suse.com Michael Stahl libreoffice-dev Data: 15 luglio 2013 16.08.16 CEST Oggetto: Re: Building LO 4.0.4.2 on illumos based OS Ok. I see. Problem is, I could easily build, package and install my xmlsec1 component in few minutes, and it did see all the required libs (openssl, and so on). How can I debug why the LO internal configure cannot see the deps? Gabriele. ---------------------------------------------------------------------------------- Da: Rene Engelhard A: Gabriele Bulfon Cc: Michael Stahl michael.me...@suse.com libreoffice-dev Data: 15 luglio 2013 16.05.26 CEST Oggetto: Re: Building LO 4.0.4.2 on illumos based OS On Mon, Jul 15, 2013 at 03:48:15PM +0200, Gabriele Bulfon wrote: I see no switch in global configure to force it to use system xmlsec. Yes, there is none... How does it decide to install its own? By just doing it unconditionally and everywhere. One possibility is that I make and install my own component of xmlsec. Will the build system see it and decide not to build its own? Nope. It's so heavily patched that it *might* build but not work afaicr. system-xmlsec was once tried by abandonded for that reason. :/ (It's - besides rhino - the only library which is needed internally...) Regards, Rene _______________________________________________LibreOffice mailing listLibreOffice@lists.freedesktop.orghttp://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
