Bug#880996: ring: FTBFS on mips64el

[James Cowgill]

Hi,

On 06/11/17 19:48, Sebastian Ramacher wrote:
> Source: ring
> Version: 20170912.1.912f772~dfsg1-2
> Severity: serious
> Tags: sid buster
> Control: block 880355 by -1
> 
> ring FTBFS on mips64el during the libva transition:
[...]
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `ring::RingAccount::useIdentity(std::pair<std::shared_ptr<dht::crypto::PrivateKey>, std::shared_ptr<dht::crypto::Certificate> > const&)':
> | ./daemon/src/ringdht/ringaccount.cpp:845: undefined reference to `dht::Value::msgpack_unpack(msgpack::v1::object)'
> | ./daemon/src/ringdht/ringaccount.cpp:845: undefined reference to `dht::Value::msgpack_unpack(msgpack::v1::object)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `msgpack::v1::type::detail::convert_integer_sign<unsigned long, false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `dht::IceCandidates::msgpack_unpack(msgpack::v1::object)':
> | /usr/include/opendht/default_types.h:190: undefined reference to `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `msgpack::v1::type::detail::convert_integer_sign<unsigned long, false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `dht::IceCandidates::msgpack_unpack(msgpack::v1::object)':
> | /usr/include/opendht/default_types.h:190: undefined reference to `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `msgpack::v1::type::detail::convert_integer_sign<unsigned long, false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o):/usr/include/opendht/default_types.h:190: more undefined references to `dht::unpackBlob(msgpack::v1::object&)' follow
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function `msgpack::v1::adaptor::convert<dht::crypto::RevocationList, void>::operator()(msgpack::v1::object const&, dht::crypto::RevocationList&) const':
> | /usr/include/msgpack/v1/object.hpp:209: undefined reference to `dht::crypto::RevocationList::msgpack_unpack(msgpack::v1::object)'
> | /usr/include/msgpack/v1/object.hpp:209: undefined reference to `dht::crypto::RevocationList::msgpack_unpack(msgpack::v1::object)'
> | collect2: error: ld returned 1 exit status
> | Makefile:628: recipe for target 'dring' failed

The problem is that ring forces the use of the msgpack v1 API, but
opendht uses whatever the default msgpack API was when it was built.
When opendht was originally uploaded this was v1 and everything was
good. Around 1 month ago, opendht was binNMUed on just mips64el and this
caused the mips64el version of opendht to use v2 of the API. Ring then
FTBFS on mips64el because it tried to use the v1 functions which don't
exist anymore.

There needs to be some agreement between ring and opendht as to what
msgpack API to use (both use v1 or v2). I'm not sure what the best
option is, but I would guess that forcing opendht to v1 would fix this.

Thanks,
James

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20171107/c1363a01/attachment.sig>