That is interesting as I can see some obvious differences in your config.log
vs. mine. In mine, it clearly indicates that it found the xerces installation
but the xalan test commands fail to find xerces references. I don't understand
that. I assume you are adding your xerces install path into the PKG_CONFIG_PATH
variable or are you instructing it where to find xerces in some other way?
I tried to run the commands differently without the environment variables like
so and the results were the same.
PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/data/${USER}/repos/tp/xerces-c-3.2.4-install/release/lib/pkgconfig:/data/${USER}/repos/tp/openssl-102u-install/release/lib/pkgconfig
./configure --prefix=/data/shawn.fox/repos/tp/santuario-2.0.4-install/release
--with-xalan=/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release
--with-openssl
Here are some follow up questions about your config.log
1) Are you not using openssl or is the --with-openssl option not needed any
longer if the path to it is in the PKG_CONFIG_PATH?
2) You didn't specify a --prefix so how will the resulting files be installed?
./configure --with-xalan=/opt/local
3) are the following version combinations acceptable? The santuario website
implies that xalan 1.11.0+ is needed so I assume that xalan 1.12.0 is
acceptable too since that is what is recommended for use with xerces 3.2.4 by
the xerces/xalan websites. Also I am having the same issues with xalan 1.11.0
so I don’t think that it is due to the version of xalan I'm using.
Openssl 1.0.2.u
xerces 3.2.4
xalan 1.12.0
Within my config.log I can see that xerces was found and these paths are all
correct.
$PKG_CONFIG --exists --print-errors " xerces-c >= 3.2"
pkg_cv_xerces_CFLAGS='-I/data/shawn.fox/repos/tp/xerces-c-3.2.4-install/release/include
'
pkg_cv_xerces_LIBS='-L/data/shawn.fox/repos/tp/xerces-c-3.2.4-install/release/lib
-lxerces-c '
There are no openssl errors either so it seems to have found openssl just fine.
openssl_CFLAGS='-I/data/shawn.fox/repos/tp/openssl-102u-install/release/include
'
openssl_LIBS='-L/data/shawn.fox/repos/tp/openssl-102u-install/release/lib
-lcrypto '
Based on the above, I'm perplexed about these errors in the g++ tests. I don't
even see the same number of g++ tests for xalan in your config.log.
g++ -o conftest -I/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/src
-I/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/include
-I/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/nls/include -g -O2
-m64 -g conftest.cpp
-L/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/lib -lxalan-c >&5
/opt/rh/gcc-toolset-12/root/usr/libexec/gcc/x86_64-redhat-linux/12/ld: warning:
libxerces-c-3.2.so, needed by
/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/lib/libxalan-c.so,
not found (try using -rpath or -rpath-link)
/opt/rh/gcc-toolset-12/root/usr/libexec/gcc/x86_64-redhat-linux/12/ld: warning:
libxalanMsg.so.112, needed by
/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/lib/libxalan-c.so,
not found (try using -rpath or -rpath-link)
/opt/rh/gcc-toolset-12/root/usr/libexec/gcc/x86_64-redhat-linux/12/ld:
/data/shawn.fox/repos/tp/xalan_c-1.12-gxp-install/release/lib/libxalan-c.so:
undefined reference to
-----Original Message-----
From: Cantor, Scott <[email protected]>
Sent: Wednesday, November 29, 2023 5:09 AM
To: [email protected]
Subject: Re: Apache Santuario config states that libcrypto is not found
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click
on a link, decrypt/open an attachment, or enable macros. For further
information on how to spot phishing, access “Cybersecurity OneSpace Page” and
report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
> Does anyone have a copy of an old config.log output to share that
> would show me what the output looks like after a successful configure?
One of mine from a Mac is attached. All of that environment stuff is long dead,
none of that is required for this build, and some of it might even break the
build if there are legacy bits left around in the script.
I believe Xalan is the lone case not relying on pkgconfig, probably due to it
not having the support for it at some point, so that's why it's specified by
path.
-- Scott
