Bug#797623: opensaml2: transition needed for g++-5 ABIs

[Ferenc Wagner]

Russ Allbery <rra at debian.org> writes:

> Ferenc Wagner <wferi at niif.hu> writes:
>
>> Thanks.  Regarding xmltooling, We could as well do a regular upload
>> replacing the liblog4cpp5-dev dependency of libxmltooling-dev with
>> liblog4shib-dev.  I only noticed this yesterday when building opensaml
>> pulled in log4cpp, sorry.
>
> I think I was just confused and everything is fine, since the transition
> already happened after the previous NMU.  There's still a transition for
> opensaml2 and shibboleth-sp2, I think, but that's tiny and not a big deal.

Do you mean the library name transition (+v5), of which this bug is
about?

> It's probably fine to upload opensaml2 right away, but I'll wait until
> log4shib propagates everywhere just in case.

Looks like it won't, the builds fail everywhere.  At first sight the
problem seems to be that on amd64:

checking if gcc static flag -static works... no

which leads to liblog4shib.la being created, while on other arches:

checking if gcc static flag -static works... yes

and liblog4shib.la is not created, leading to an error when debian/rules
tries to remove it.  While this would be easy to work around, I really
wonder what's going on.  Looking at my older build logs, the -static
flag occasionally worked on amd64, but most of the it does not work
(according to configure).  Why does this happen?
-- 
Thanks,
Feri.