-
Notifications
You must be signed in to change notification settings - Fork 56
Building XMLSec
XMLSec source code can be built for Linux on z Systems running RHEL 7.1/6.6, SLES 12/11 and Ubuntu 16.04 by following these instructions. Version 1.2.22 has been successfully built & tested this way.
General Notes:
i) When following the steps below please use a standard permission user unless otherwise specified.
ii) 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
For RHEL 7.1
sudo yum install git make libtool libxslt-devel libtool-ltdl-develFor SLES 12
sudo zypper install git-core gcc make libtool libxslt-devel libopenssl-devel-1.0.1i-2.12.s390xFor RHEL 6.6
sudo yum install tar git make libtool libxslt-devel libtool-ltdl-develFor SLES 11
sudo zypper install tar pkg-config autoconf automake git-core gcc make libtool libxslt-develFor Ubuntu 16.04
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_22- 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: xmlSecGetDefaultCrypto
The 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.