MacPorts Shibboleth SP 2.5.5 defunct?

[Michael Stroucken]

On 9/3/15 10:09, Cantor, Scott wrote:
> On 9/3/15, 9:57 AM, "dev on behalf of Lukas Hämmerle" <dev-bounces at shibboleth.net on behalf of lukas.haemmerle at switch.ch> wrote:
>> I freshly installed MacPorts on a clean Mac OS X 10.10.5, then installed
>> Shibboleth. This seems to work better, at least "shibd -t" returns what
>> one would expect.
> Ok. Seems like we need to test 10.9 to be sure, don't know if I have an unupgraded Mac I can try. Hopefully you might have one...
>
>> So, the cause could indeed be that my colleague's and my MacPort
>> installation is from an earlier Mac OS X version. Will do a complete
>> uninstall and reinstall of MacPorts tomorrow to see if that helps.
> Ok.
>
> Note that I find that requirement pretty ridiculous, practically disqualifying for a production environment. I was going to look into HomeBrew to see if they had anything similar. I don't think forcing a reinstall of software after a minor OS upgrade is a reasonable thing to ask.
>
Personally, I'm waiting for rtorrent to be compilable under MacPorts
again - it seems to be just a conflict between the upstream source using
"tr1/*" includes, and the current Mac compiler environment having
included those now in the main include path with the adoption of C++11.

MacPorts has to do catch-up with whatever Apple decides to do every time
they release an update. I think long-time users of MacPorts have seen
annoyances like this before, and a while back people with Linux binaries
could have lost their function when their distro updated the library
version on a minor upgrade.

Statically linking may help :)

But in this case there is a SIGSEGV, so a backtrace of the crash could
be useful.

Greetings,
Michael.