-
Notifications
You must be signed in to change notification settings - Fork 56
Building XMLSec
Below versions of XMLSec are available in respective distributions:
- RHEL 6.8 has
1.2.20 - RHEL 7.1/7.2/7.3 has
1.2.20 - Ubuntu 16.04/16.10 has
1.2.20
The instructions provided below specify the steps to build XMLSec 1.2.23 on IBM z Systems for RHEL 6.8/7.1/7.2/7.3, SLES 11-SP4/12/12-SP1/12-SP2 and Ubuntu 16.04/16.10.
General Notes:
-
When following the steps below please use a standard permission user unless otherwise specified.
-
A directory
/<source_root>/will be referred to in these instructions, this is a temporary writeable directory anywhere you'd like to place it
- Use the following commands to obtain dependencies
RHEL 6.8
sudo yum install tar git make libtool libxslt-devel libtool-ltdl-develRHEL 7.1/7.2/7.3
sudo yum install git make libtool libxslt-devel libtool-ltdl-develSLES 11-SP4
sudo zypper install tar pkg-config autoconf automake git-core gcc make libtool libxslt-devel awkSLES 12/12-SP1/12-SP2
sudo zypper install git-core gcc make libtool libxslt-devel libopenssl-develUbuntu 16.04/16.10
sudo apt-get update
sudo apt-get install git make libtool libtool-bin libxslt1-dev autoconf libxmlsec1-dev- Create a working directory with write permission to use as an installation workspace (Referred to as
/<source_root>/from this point on)
mkdir /source_root/
cd /source_root/- Download XMLSec source code
cd /<source_root>/
git clone https://github.com/lsh123/xmlsec.git
cd xmlsec
git checkout xmlsec-1_2_23- Generate and then run the configuration
./autogen.sh- Build and (optionally) test
make- Install XMLSec and verify the installation
sudo make install
make checkNote: If the following error is shown, set the environment variable "LD_LIBRARY_PATH" to path of XMLSec binaries e.g. export LD_LIBRARY_PATH=/usr/local/lib
xmlsec1: error while loading shared libraries: libxmlsec1.so.1: cannot open shared object file: No such file or directoryor
xmlsec1: symbol lookup error: xmlsec1: undefined symbol: xmlSecGetDefaultCryptoThe information provided in this article is accurate at the time of writing, but on-going development in the open-source projects involved may make the information incorrect or obsolete. Please open issue or contact us on IBM Z Community if you have any questions or feedback.