Re: Building LO 4.0.4.2 on illumos based OS

For now, it's ok to have the build go through, so I can see if I can reach a working LO.
Then I'll dig again the NSS problem, and see if I can support it.
Now: build reached the "install creation" phase!
But: something went wrong.
USAGE: 
/sources/userlands/xstream-userland-gate/components/libreoffice/libreoffice-4.1.0.1/setup_native/scripts/install_create.pl
: the start shell script, located next to this perl script
: the library file, that is included into the shell script
: the target shellscript
chmod: cannot access 
'/sources/userlands/xstream-userland-gate/components/libreoffice/libreoffice-4.1.0.1/workdir/unxsogi.pro/CustomTarget/setup_native/scripts/install':
 No such file or directory
make[2]: *** 
[/sources/userlands/xstream-userland-gate/components/libreoffice/libreoffice-4.1.0.1/workdir/unxsogi.pro/CustomTarget/setup_native/scripts/install]
 Error 1
As if the install creation did not pass arguments to the perl script.
Actually, I don't want it to create an installer for solaris via packages.
What I want is to issue some kind of "gmake install" to let it place everything inside a prototype 
area,
through classic configure switches.
This will let me publish the package in my IPS repository, as for any SunOS 5.11 based system.
Any idea how to achieve this?
Gabriele.
----------------------------------------------------------------------------------
Da: Michael Stahl
A: Gabriele Bulfon
Cc: libreoffice-dev
michael.meeks@suse.com Rene Engelhard
Data: 16 luglio 2013 10.43.01 CEST
Oggetto: Re: Building LO 4.0.4.2 on illumos based OS
On 16/07/13 08:09, Gabriele Bulfon wrote:
Now I noticed the config.log of xmlsec shows the configure switches like
this:
./configure --with-pic --disable-shared --disable-crypto-dl
--without-libxslt --without-gnutls --without-openssl
This is why it's not picking up my system openssl not the other crypto libs.
I bet it's trying to build it only with NSS libs, but they're not passed
correctly (they resides
in /usr/lib/mps in my environment) from base env.
Is it absolutely necessary that it builds without those crypto libs?
i'm not entirely sure but i think that the ODF encryption support (which
is the only use of libxmlsec) on Unixes is implemented by using keys
added by Firefox/Thunderbird UI to their user profiles; there is no UI
in LO for adding/removing keys.  probably only NSS can read the
Firefox/Thunderbird key database, so i'm afraid that if you build xmlsec
with anything other than NSS it won't work in practice.