Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH linux
Shaik, Abdul (NBCUniversal)
Abdul.Shaik at nbcuni.com
Tue Dec 27 00:18:20 GMT 2011
I am seeing the following error after building the supporting packages
using RPMs and tried to build shibboleth with enable apache22 options.
Command Ran to build shibboleth: ./configure --enable-apache-22
--with-apxs2=/usr/local/apache2/bin/apxs
I downloaded all the RPMs from
http://download.opensuse.org/repositories/security://shibboleth/RHEL_4/i
386/
<http://download.opensuse.org/repositories/security:/shibboleth/RHEL_4/i
386/>
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.
checking whether the compiler supports Standard Template Library... yes
checking for ctime_r... yes, and it takes 2 arguments
checking for log4shib-config... /usr/local/bin/log4shib-config
checking log4shib/CategoryStream.hh usability... yes
checking log4shib/CategoryStream.hh presence... yes
checking for log4shib/CategoryStream.hh... yes
checking xercesc/dom/DOM.hpp usability... yes
checking xercesc/dom/DOM.hpp presence... yes
checking for xercesc/dom/DOM.hpp... yes
checking Xerces version... OK
checking whether Xerces XMLString::release(XMLByte**) exists... no
checking whether Xerces DOMNodeFilter API returns a short... no
checking xsec/utils/XSECPlatformUtils.hpp usability... yes
checking xsec/utils/XSECPlatformUtils.hpp presence... yes
checking for xsec/utils/XSECPlatformUtils.hpp... yes
checking XML-Security-C version... OK
checking whether XML-Security-C supports white/blacklisting of
algorithms... no
checking xmltooling/base.h usability... yes
checking xmltooling/base.h presence... yes
checking for xmltooling/base.h... yes
configure: error: unable to link with XMLTooling, or version was too old
Could you please let us know how to correct this?
-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Shaik, Abdul (NBCUniversal)
Sent: Monday, December 26, 2011 5:16 PM
To: Shib Users
Subject: RE: Need help in shiibboleth upgrade from 2.3.1 to 2.4.3 on RH
linux
Thanks Scott for the clarification.
Is there a documentation on how to remove the packages installed by
using
SRPMs(log4shib+opensaml+xerces+xmltooling etc).
I removed all the packages installed by RPM. I just want to make sure
that there
is nothing remained from the installation of SRPMs.
We initially installed shibboleth and other supporting packages on this
box
using SRPMs.
Appreciate your help on this.
--Kalam
-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Cantor, Scott
Sent: Monday, December 19, 2011 6:16 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/19/11 5:39 PM, "Shaik, Abdul (NBCUniversal)"
<Abdul.Shaik at nbcuni.com> wrote:
>Hi All,
>
>We are trying to upgrade
>shibboleth from 2.3.1 to 2.4.3 using rpm source.
You're mixing versions of packages during the build.
>The problem is when
>installing the packages libsaml7-2.4.3-3.1.i386.rpm and
>opensaml-bin-2.4.3-3.1.i386.rpm, it still requires old library from the
>previous installation: error: Failed dependencies:
The only libraries it requires are the ones you build it against.
>libxml-security-c.so.15 is needed by libsaml7-2.4.3-3.1.i386 and it
>should look
>for new library libxml-security-c.so.16.
If it requires .so.15, then that's because the package(s) you had in
place
during the SRPM rebuild were from that version. Certainly the devel
package was.
> And we have both new and old library
>file: libxml-security-c.so.15 and libxml-security-c.so.16 needed to
>support the
>package
That doesn't matter. If the build is linked to one version, that's the
version that will be embedded in the RPM that results.
If you want to use xml-security-1.6.1 and build on a box that has a
running version of older software, you have to take care to remove at
minimum all the old -devel packages and install the new lib and -devel
packages along side the old lib packages rather than doing upgrades.
Then
the new builds on top will use the latest version found.
I would question why you're doing any of this. As long as RH4 remains
supported, which ends with the next release, but for now anyway, there's
no reason you should be building this from source. The shibboleth
package
alone might require a rebuild if your Apache isn't standard, but that
doesn't require rebuilding the rest.
You also shouldn't be trying to build a new set of packages on a machine
running an older version. You can, but you're not being successful, so
you
should consider using a clean box to build the packages and then
transfer
them.
-- Scott
--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20111226/828fa2f2/attachment-0001.html
More information about the users
mailing list