Bug#797623: opensaml2: transition needed for g++-5 ABIs
Ferenc Wagner
wferi at niif.hu
Sun Jan 17 08:05:50 UTC 2016
Russ Allbery <rra at debian.org> writes:
> Ferenc Wagner <wferi at niif.hu> writes:
>
>> 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?
>
> The rm command for removing liblog4shib.la hard-coded the multiarch path
> for amd64. I just uploaded a new version of the package that should fix
> it.
I totally misled myself, thanks for fixing this up. I still wonder
why -static does not work on amd64, though...
Meanwhile I pushed two small fixups for xmltooling, please sponsor the
upload if you agree.
--
Thanks,
Feri.
More information about the Pkg-shibboleth-devel
mailing list