mod_shib_22.so missing after SRPM rebuild process

[Jen Hong]

Scott/Michael:

We tried with rhel option, still did not build the shib apache modules for us.  Back to drawing board.  Did anyone have any challenges in doing the SRPM rebuild?

Regards,
Jen

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, August 30, 2017 1:53 PM
To: Shib Users
Subject: Re: mod_shib_22.so missing after SRPM rebuild process

On 8/30/17, 4:43 PM, "users on behalf of Michael Young" <users-bounces at shibboleth.net on behalf of m.a.young at durham.ac.uk> wrote:

> I think you said in another message that you are on OEL6, which I 
> don't think is supported in the spec file, so it isn't getting the 
> apache build status right. You might be able to fool it by pretending to be RHEL, eg.
> by adding --define="rhel 6" to the rpmbuild command.

Given that it's a clone I kind of figured it would report out as rhel, but that opens up a range of complex specfile interactions.

But, that should only affect the installation of the module's sample config file and very light Apache touchpoints during the package install like restarting it on updates. It should not prevent the module from being built or installed to /usr/lib64/shibboleth that I can see from a glance, that's all just done by autoconf tests (or configure options but that isn't something that should be needed for a default build).

In fact, a lot of the stuff the RPM install does are triggered by the mere fact the module library is present in the built tree. It uses the rhel macros for some things like establishing dependencies (e.g. it would allow it to know httpd-devel wasn't there but was required).

Good thought though (or I'm just wrong, but I don't think I am).

-- Scott


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