[Lasso-devel] Problem when loading Lasso on RedHat 64bits

[Benjamin Dauvergne]

Clément OUDOT écrivait:
> 2011/12/16 Benjamin Dauvergne <bdauvergne at entrouvert.com>:
> > Clément OUDOT écrivait:
> >> [root at localhost ~]# cat /usr/lib/pkgconfig/xmlsec1.pc
> >> prefix=/usr
> >> exec_prefix=/usr
> >> libdir=/usr/lib
> >> includedir=/usr/include
> >>
> >> Name: xmlsec1
> >> Version: 1.2.9
> >> Description: XML Security Library implements XML Signature and XML
> >> Encryption standards
> >> Requires: libxml-2.0 >= 2.6.12 libxslt >= 1.0.20
> >> Cflags: -DXMLSEC_CRYPTO=\\\"openssl\\\"
> >> -DXMLSEC_CRYPTO_DYNAMIC_LOADING=1  -D__XMLSEC_FUNCTION__=__FUNCTION__
> >> -DXMLSEC_NO_XKMS=1 -I/usr/include/xmlsec1
> >> Libs: -L${libdir} -lxmlsec1  -ldl
> >>
> >> So it seems we have -DXMLSEC_CRYPTO_DYNAMIC_LOADING=1, you confirm?
> > Yes it seems that on RHEL 5.3 loading at runtime is the default. But the
> > loading still fails in Lasso. I would compile lasso and launch the tests
> > just to verify that it works when compiled on RHEL 5.3 without making
> > a package.
> 
> Hi,
> 
> should I fill a bug on https://dev.entrouvert.org/projects/lasso ?
What is the bug ? Did you compile Lasso on CentOS ? Did it fail to run 
the test suite ?

> By the way, the link "Bug reports" on http://lasso.entrouvert.org/ is
> false, it links to bugzilla, which seems down.
Good catch. I changed it for the redmine.

-- 
"Java is a DSL for taking large XML files and converting them to stack traces"