Hello,
I'd appreciate some help in understanding the changes to the build
configuration., and I have read what guidelines exist on the Apache Santuario
home page, but it isn't clear to me why the configure script for Santuario
2.0.4 isn't finding the XalanVersion.hpp file. It sure looks like the
config.log file indicates the correct location for the xalan installation with
the headers and binary artifacts from the xalan 1.11.0 build but reports that
it can't find a header file.
With Santuario 1.7.3 I did something like this,
# Create some env variables to make configure easier (release mode first):
# These variables are where gmake install puts the artifacts after building
those products from the source
export XERCESCROOT=/data/your.name/xerces/release
export XALANCROOT=/data/your.name/xalan/release
export OPENSSL_INSTALL=/data/your.name/openssl
# - Run configure and build for release mode build
# example - export
SANTUARIO_INSTALL=/data/$USER/repos/tp/santuario-1.7.3-install/debug
export SANTUARIO_INSTALL=/data/$USER/santuario-1.7.3-install/debug
./configure \
--prefix=$SANTUARIO_INSTALL \
--enable-debug \
--with-xerces=$XERCESCROOT \
--with-xalan=$XALANCROOT \
--with-openssl=$OPENSSL_INSTALL \
CFLAGS=-m64 CPPFLAGS=-m64
Now Santuario 2.0.4 has a different configure script and there is no longer a
--with-xerces option so I had to add the path to the .pc file for xerces to
something like this:
echo $PKG_CONFIG_PATH
/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig:/data/$USER/repos/tp/xerces-c-3.2.4-install/release/lib/pkgconfig
Now I am running the config script like this
./configure \
--prefix=$SANTUARIO_INSTALL \
--with-xalan=$XALANCROOT \
--with-openssl=$OPENSSL_INSTALL \
CPPFLAGS='-m64 -g'
Now the problem is that the conf.log indicates trouble finding xalan include
files which I don't understand. It seems to know where to look for the xalan
installation, and I have confirmed that the include files are present under
/data/$USER/repos/tp/xalan-1.11.0-gxp-4-install/release/include.
ls
/data/shawn.fox/repos/tp/xalan-1.11.0-gxp-4-install/release/include/xalanc/Include/
AIXDefinitions.hpp IntelDefinitions.hpp PlatformDefinitions.hpp
TRU64Definitions.hpp XalanDeque.hpp XalanMemMgrAutoPtr.hpp
XalanObjectStackCache.hpp XalanVersion.hpp
GCCDefinitions.hpp OS390Definitions.hpp SolarisDefinitions.hpp
VCPPDefinitions.hpp XalanList.hpp XalanMemoryManagement.hpp XalanSet.hpp
HPUXDefinitions.hpp OS400Definitions.hpp STLHelper.hpp
XalanAutoPtr.hpp XalanMap.hpp XalanObjectCache.hpp XalanVector.hpp
However, I still see this error generated into config.log. The -I option looks
correct and you can see in the above text that XalanVersion.hpp does exist.
configure:17921: checking xalanc/Include/XalanVersion.hpp usability
configure:17921: g++ -c
-I/data/shawn.fox/repos/tp/xalan-1.11.0-gxp-4-install/release/src
-I/data/shawn.fox/repos/tp/xalan-1.11.0-gxp-4-install/release/include
-I/data/shawn.fox/repos/tp/xalan-1.11.0-gxp-4-install/release/nls/include -g
-O2 -m64 -g conftest.cpp >&5
configure:17921: $? = 0
configure:17921: result: yes
configure:17921: checking xalanc/Include/XalanVersion.hpp presence
configure:17921: g++ -E -m64 -g conftest.cpp
conftest.cpp:27:10: fatal error: xalanc/Include/XalanVersion.hpp: No such file
or directory
27 | #include <xalanc/Include/XalanVersion.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
configure:17921: $? = 1
Am I misunderstanding something about the changes to the configure script?
Thanks,
Shawn Fox
