[Open Office] problem with OOo file digital signature ( using --with-system-xmlsec ) in m179

[Giuseppe Castagno]

Hi all,

my system:
FC5, gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)

libxmlsec1:
[beppe at nbklx program]$ rpm -qa xmlsec\*
xmlsec1-nss-1.2.9-4.2
xmlsec1-debuginfo-1.2.9-4.2
xmlsec1-devel-1.2.9-4.2
xmlsec1-nss-devel-1.2.9-4.2
xmlsec1-1.2.9-4.2

[beppe at nbklx beppe]$ rpm -qa nss\*
nss-devel-3.11.1-1.fc5
nss_db-2.2-35
nss-3.11.1-1.fc5
nss_ldap-249-1

Top of ooo-build/ChangeLog:

2006-08-01  Noel Power  <noel.power at novell.com>

	* patches/vba/extensions-source-propctrlr-makefile-mk.diff: removed
	unused patches
	* patches/vba/extensions-source-propctrlr-formcontroller-cxx.diff:
	* patches/vba/vba-runtime-vba-enabled.diff:

2006-08-01  Michael Meeks  <michael.meeks at novell.com>

Up to m177 I was able to compile using the local libxmlsec (1.2.6),
until then no problem popped up.

Starting with m179 I was no longer able to compile with  the local
xmlsec library.
With the following configure flags, added to CommonLinux.conf:

--with-system-neon
--with-system-expat
--with-system-curl
--with-system-boost
--with-system-sane-headers
--with-system-sndfile
--with-system-libxslt
--with-ant-home=/opt/apache-ant-1.6.5
--with-jdk-home=/usr/java/jdk1.5.0_06
--without-myspell-dicts
--enable-crypt-link
--enable-gnome-vfs
--enable-kde
--enable-gtk
--enable-lockdown
--disable-odk
--disable-qadevooo

 The libxmlsec configuration stopped with:
...

checking libxml2   yes  ... checking for libxslt libraries >= 1.0.20... no
checking for openssl libraries >= 0.9.6... no
checking for gnutls libraries >= 0.8.1... no
checking for mozilla-nspr >= 1.4 mozilla-nss >= 1.4... checking for
nspr libraries >= 4.0... no
checking for nss libraries >= 3.2... no
checking for crypto library... configure: error: At least one crypto
library should exist for xmlsec1
dmake:  Error code 1, while making
'./unxlngi6.pro/misc/build/so_configured_so_xmlsec1'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/media/usb-1/home/beppe/ooo-b-m179/build/src680-m179/libxmlsec
make: *** [stamp/build] Error 1

The patch that allowed the local compilation (with nss) was
buildfix-system-nss.diff, if I recall; it's no longer there.

So I tried to use --with-system-xmlsec, the compilation ended
successfully, but part of the libxmlsec functionality disappeared.

The configure flags I used in this case, added to CommonLinux.conf, were:

--with-system-neon
--with-system-expat
--with-system-curl
--with-system-boost
--with-system-sane-headers
--with-system-sndfile
--with-system-libxslt
--with-system-xmlsec
--with-ant-home=/opt/apache-ant-1.6.5
--with-jdk-home=/usr/java/jdk1.5.0_06
--without-myspell-dicts
--enable-crypt-link
--enable-gnome-vfs
--enable-kde
--enable-gtk
--enable-lockdown
--disable-odk
--disable-qadevooo

OOo encrypt the files, but no signing is possible.
I tried to investigate and it seems that libxmlsec1 is badly initialized.

Did someone experience the same problem ? Or there is still a way to
compile the local libxmlsec with system nss ?

I have a 2.0.3 (compiled with local xmlsec) installed on the same PC
that can sign the OOo files, so I think that's not a problem with
mozilla or firefox.

-- 
Kind regards,
Giuseppe Castagno