Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH linux

[Shaik, Abdul (NBCUniversal)]

Scott,

I followed the following process after completely removing the existing
installation of shibbolet 2.3.1

downloaded all the packages from
http://download.opensuse.org/repositories/security://shibboleth/RHEL_4/i
386/

Installed the packages using RPM in the following order:

log4shib
xerces-c
xml-security-c
xmltooling
opensaml

1. [root at useclwslp019 shibpackages2.4.2]# rpm -ivh
log4shib-1.0.3-2.1.i386.rpm
warning: log4shib-1.0.3-2.1.i386.rpm: V3 DSA signature: NOKEY, key ID
7d0a1b3d
Preparing...                ###########################################
[100%]
   1:log4shib               ###########################################
[100%]

2. [root at useclwslp019 shibpackages2.4.2]# rpm -ivh
xerces-c-3.0.1-6.1.i386.rpm
warning: xerces-c-3.0.1-6.1.i386.rpm: V3 DSA signature: NOKEY, key ID
7d0a1b3d
Preparing...                ###########################################
[100%]
   1:xerces-c               ###########################################
[100%]


3.[root at useclwslp019 shibpackages2.4.2]# rpm -ivh
xml-security-c-1.5.1-4.1.i386.rpm
warning: xml-security-c-1.5.1-4.1.i386.rpm: V3 DSA signature: NOKEY, key
ID 7d0a1b3d
Preparing...                ###########################################
[100%]
   1:xml-security-c         ###########################################
[100%]

4.[root at useclwslp019 shibpackages2.4.2]# rpm -ivh
xmltooling-1.3.3-1.1.i386.rpm
warning: xmltooling-1.3.3-1.1.i386.rpm: V3 DSA signature: NOKEY, key ID
7d0a1b3d
Preparing...                ###########################################
[100%]
   1:xmltooling             ###########################################
[100%]

5.[root at useclwslp019 shibpackages2.4.2]# rpm -ivh
opensaml-2.3-1.6.i386.rpm
warning: opensaml-2.3-1.6.i386.rpm: V3 DSA signature: NOKEY, key ID
7d0a1b3d
Preparing...                ###########################################
[100%]
   1:opensaml               ###########################################
[100%]


   Since we need to build shibboleth with apache22, I tried to build
from SRPM, I downlaoded shibboleth-2.4-2.2.src.rpm from 
 
http://download.opensuse.org/repositories/security://shibboleth/RHEL_4/s
rc/

I followed the instructions from
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPLinuxSRPMBu
ild to build shibboleth from SRPM.

   rpmbuild --rebuild -D 'shib_options --enable-apache-22'
shibboleth-2.4-2.2.src.rpm

   I am getting the following error. Please let me know what needs to be
done to fix. 

   [root at useclwslp019 SRPM]# rpmbuild --rebuild -D 'shib_options
--enable-apache-22' shibboleth-2.4-2.2.src.rpm
Installing shibboleth-2.4-2.2.src.rpm
warning: user abuild does not exist - using root
warning: group abuild does not exist - using root
warning: user abuild does not exist - using root
warning: group abuild does not exist - using root
error: Failed build dependencies:
        libxerces-c-devel >= 2.8.0 is needed by shibboleth-2.4-2.2.i386
        libxml-security-c-devel >= 1.4.0 is needed by
shibboleth-2.4-2.2.i386
        libxmltooling-devel >= 1.4 is needed by shibboleth-2.4-2.2.i386
        libsaml-devel >= 2.4 is needed by shibboleth-2.4-2.2.i386
        liblog4shib-devel is needed by shibboleth-2.4-2.2.i386
[root at useclwslp019 SRPM]#



-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Cantor, Scott
Sent: Tuesday, December 27, 2011 2:25 PM
To: users at shibboleth.net
Subject: Re: Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH
linux

On 12/26/11 7:18 PM, "Shaik, Abdul (NBCUniversal)"
<Abdul.Shaik at nbcuni.com> wrote:

>I checked the config log, it says that it needs xmltooling 1.4 or
>higher. I did not see this package in the above link.

Then you need to look closer, it's certainly there. If the build found
the
headers, then you either have the devel package installed, which implies
the library is also installed as a dependency of that package, or you
have
stale headers lying around from some other kind of build and the
library's
not in the same place.

Without more information from the log, or about what's installed, I have
no suggestions.

-- Scott

--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net