--with-xmlsec is not taken into account for test xmltooling version in SP build
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
The # XML-Security settings in the autoconfig script is set AFTER
AC_LINK_IFELSE( [AC_LANG_PROGRAM([[#include <xmltooling/XMLToolingConfig.h> #include <xmltooling/version.h>]], [[#if _XMLTOOLING_VERSION >= 10400 xmltooling::XMLToolingConfig::getConfig(); #else #error Need XMLTooling version 1.4 or higher #endif]])], ,[AC_MSG_ERROR([unable to link with XMLTooling, or version was too old])])
which does not allow to set a custom xml-security-c library path.
In case of the presence of an older xml-security-c version - which might be installed by the OS - the test will fail, because some symbols wan't found.
Environment
None
Activity
Show:
Scott Cantor February 17, 2011 at 11:48 PM
Testing suggests xmlsec can be located independently of xmltooling now.
Scott Cantor February 7, 2011 at 9:57 AM
Never mind then, I can test it.
Lukas Hämmerle February 7, 2011 at 4:27 AM
Edited
I should be able to test it but it would be great if you could generate the configure script using your version of autoconf. If I do it it either warns "warning: this file was generated for autoconf 2.68." or complains: configure.ac:3: error: possibly undefined macro: AM_CONFIG_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:4: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.ac:59: error: possibly undefined macro: AC_DISABLE_STATIC configure.ac:60: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:143: error: possibly undefined macro: AC_CXX_REQUIRE_STL configure.ac:144: error: possibly undefined macro: AC_CXX_NAMESPACES configure.ac:398: error: possibly undefined macro: AM_CONDITIONAL
Scott Cantor February 4, 2011 at 12:32 PM
I believe this is fixed, but would appreciate if you could test.
We've moved the code to the new repositories, so if you have a checkout, you'll need to recheckout using svn.shibboleth.net. I updated the SourceAccess page in the old wiki with the links.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The # XML-Security settings in the autoconfig script is set AFTER
AC_LINK_IFELSE(
[AC_LANG_PROGRAM([[#include <xmltooling/XMLToolingConfig.h>
#include <xmltooling/version.h>]],
[[#if _XMLTOOLING_VERSION >= 10400
xmltooling::XMLToolingConfig::getConfig();
#else
#error Need XMLTooling version 1.4 or higher
#endif]])],
,[AC_MSG_ERROR([unable to link with XMLTooling, or version was too old])])
which does not allow to set a custom xml-security-c library path.
In case of the presence of an older xml-security-c version - which might be installed by the OS - the test will fail, because some symbols wan't found.