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


...I also found that the old README.Solaris mentions a "--disable-xmlsec", but the configure script
doesn't mention it.
Any other way to avoid building xmlsec?
Da:
Gabriele Bulfon
A:
Rene Engelhard
Cc:
michael.meeks@suse.com libreoffice-dev
Michael Stahl
Data:
15 luglio 2013 16.47.25 CEST
Oggetto:
Re: Building LO 4.0.4.2 on illumos based OS
A deeper check of the xmlsec1 config.log, shows there are many vars that are empty, not passed
by main configure, such as NSS_LIBS and NSS_CFLAGS.
These are set up during configure, and I used them to build against system nspr that is in a 
different
location, but are empty in this internal xmlsec1 config.log.
Probably I could pass also other libs like OPENSSL_CFLAGS and OPENSSL_LIBS, but I should
understand how to pass them.
Da:
Gabriele Bulfon
A:
Rene Engelhard
Cc:
michael.meeks@suse.com libreoffice-dev
Michael Stahl
Data:
15 luglio 2013 16.34.41 CEST
Oggetto:
Re: Building LO 4.0.4.2 on illumos based OS
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.meeks@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.meeks@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 
listLibreOffice@lists.freedesktop.orghttp://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________LibreOffice mailing 
listLibreOffice@lists.freedesktop.orghttp://lists.freedesktop.org/mailman/listinfo/libreoffice

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.