Project

General

Profile

Bug #5062

Error bulid on CentOS release 6.5 (Final)

Added by Timour Ezizov over 10 years ago. Updated over 9 years ago.

Status:
Fermé
Priority:
Bas
Assignee:
-
Category:
-
Target version:
future
Start date:
27 June 2014
Due date:
% Done:

0%

Estimated time:
Patch proposed:
No
Planning:

Description

Can't build on Centos

Full log in attachment

lasso.c: In function 'lasso_init':
lasso.c:176: error: 'openssl' undeclared (first use in this function)
lasso.c:176: error: (Each undeclared identifier is reported only once
lasso.c:176: error: for each function it appears in.)
make4: * [lasso.lo] Error 1
make4: Leaving directory `/home/tez/tmp2/lasso-2.4.0/lasso'
make3: [all-recursive] Error 1
make3: Leaving directory `/home/tez/tmp2/lasso-2.4.0/lasso'
make2: [all] Error 2
make2: Leaving directory `/home/tez/tmp2/lasso-2.4.0/lasso'
make1: [all-recursive] Error 1
make1: Leaving directory `/home/tez/tmp2/lasso-2.4.0'
make: ** [all] Error 2

[tez@localhost lasso-2.4.0]$ uname -a
Linux localhost.localdomain 2.6.32-431.20.3.el6.i686 #1 SMP Thu Jun 19 19:51:30 UTC 2014 i686 i686 i386 GNU/Linux

Files

lasso_2.4_error.txt (15.2 KB) lasso_2.4_error.txt Timour Ezizov, 27 June 2014 02:14 PM
lasso_64_build_error.txt (15.3 KB) lasso_64_build_error.txt Timour Ezizov, 27 June 2014 03:56 PM

History

#1

Updated by Timour Ezizov over 10 years ago

In CentOS 6 64 bit same situation
Log attached.

#2

Updated by Timour Ezizov over 10 years ago

Changing lasso.c file line 178
- if (xmlSecCryptoDLLoadLibrary(BAD_CAST XMLSEC_CRYPTO)
+ if (xmlSecCryptoDLLoadLibrary(BAD_CAST "openssl")

did the trick, but...

#3

Updated by Frédéric Péters over 10 years ago

It looks like mssing quotes in the xmlsec1-openssl.pc file, could you check?

$ pkg-config --cflags xmlsec1-openssl
-DXMLSEC_CRYPTO=\"openssl\" -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_SIZE_T -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_XKMS=1 -DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -DXMLSEC_OPENSSL_098=1 -DXMLSEC_CRYPTO_OPENSSL=1 -I/usr/include/libxml2 -I/usr/include/xmlsec1
#4

Updated by Timour Ezizov over 10 years ago

So,
if I run:

pkg-config --cflags xmlsec1-openssl
-DXMLSEC_CRYPTO="openssl" -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_XKMS=1 -DXMLSEC_DL_LIBLTDL=1 -DXMLSEC_OPENSSL_100=1 -DXMLSEC_CRYPTO_OPENSSL=1 -I/usr/include/xmlsec1 -I/usr/include/libxml2

but file self is:

cat /usr/lib/pkgconfig/xmlsec1-openssl.pc
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include

Name: xmlsec1-openssl
Version: 1.2.19
Description: XML Security Library implements XML Signature and XML Encryption standards
Requires: libxml-2.0 >= 2.7.4 libxslt >= 1.0.20 
Cflags: -DXMLSEC_CRYPTO=\"openssl\"  -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_XKMS=1 -DXMLSEC_DL_LIBLTDL=1 -I/usr/include/xmlsec1     -DXMLSEC_OPENSSL_100=1 -DXMLSEC_CRYPTO_OPENSSL=1
Libs: -L/usr/lib -lxmlsec1-openssl -lxmlsec1 -lltdl  -lssl -lcrypto

also I found bug http://www.freebsd.org/cgi/query-pr.cgi?pr=152070 related to LASSO

and if I revert xmlsec1-openssl.pc file to (triple backslash \\\) then I have correct output

pkg-config --cflags xmlsec1-openssl
-DXMLSEC_CRYPTO=\"openssl\" -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_GOST=1 -DXMLSEC_NO_XKMS=1 -DXMLSEC_DL_LIBLTDL=1 -DXMLSEC_OPENSSL_100=1 -DXMLSEC_CRYPTO_OPENSSL=1 -I/usr/include/xmlsec1 -I/usr/include/libxml2

and can't build

Errors like this:

ake[5]: Entering directory `/home/tez/dev/lasso-2.4.0/lasso/xml/saml-2.0'
  CC     saml2_action.lo
<command-line>: warning: "XMLSEC_CRYPTO" redefined
<command-line>: warning: this is the location of the previous definition
  CC     saml2_advice.lo
<command-line>: warning: "XMLSEC_CRYPTO" redefined
<command-line>: warning: this is the location of the previous definition
  CC     saml2_assertion.lo

#5

Updated by Benjamin Dauvergne almost 10 years ago

  • Priority changed from Haut to Bas
#6

Updated by Benjamin Dauvergne over 9 years ago

  • Target version set to future
#7

Updated by Benjamin Dauvergne over 9 years ago

  • Status changed from Nouveau to Fermé

Bug was in the .pc file.

Also available in: Atom PDF