Your message dated Tue, 11 Jul 2017 06:34:19 +0000
with message-id <[email protected]>
and subject line Bug#847976: fixed in qpid-proton 0.14.0-5.1
has caused the Debian Bug report #847976,
regarding qpid-proton: FTBFS on mips and mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
847976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847976
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: qpid-proton
Version: 0.14.0-4
Severity: important
Tags: patch

Hi,

qpid-proton FTBFS on mips and mipsel with the error:
> CMakeFiles/mt_broker.dir/mt/epoll_container.cpp.o: In function 
> `std::__atomic_base<unsigned long long>::operator++()':
> /usr/include/c++/6/bits/atomic_base.h:296: undefined reference to 
> `__atomic_fetch_add_8'
> /usr/include/c++/6/bits/atomic_base.h:296: undefined reference to 
> `__atomic_fetch_add_8'
> CMakeFiles/mt_broker.dir/mt/broker.cpp.o: In function 
> `std::__atomic_base<unsigned long long>::fetch_add(unsigned long long, 
> std::memory_order)':
> /usr/include/c++/6/bits/atomic_base.h:514: undefined reference to 
> `__atomic_fetch_add_8'
> /usr/include/c++/6/bits/atomic_base.h:514: undefined reference to 
> `__atomic_fetch_add_8'
> collect2: error: ld returned 1 exit status
> examples/cpp/CMakeFiles/mt_broker.dir/build.make:127: recipe for target 
> 'examples/cpp/mt_broker' failed

This error is due to the use of 8-byte atomics which are not natively
supported on 32-bit MIPS. To fix this you have to use GCC's libatomic
library which emulates the atomics using locks. I've attached a patch
which fixes this.

Thanks,
James
Description: Link mt_broker example with -latomic
 On MIPS (and probably other) platforms, 8-byte atomics are not supported on the
 hardware level. To allow 8-byte atomics to be used on these platforms, GCC
 provides the libatomic library which implements them using locks.
 .
 Since the mt_broker example uses 8-byte atomics, link it with -latomic to
 allow atomics to work on MIPS.
Author: James Cowgill <[email protected]>
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/examples/cpp/CMakeLists.txt
+++ b/examples/cpp/CMakeLists.txt
@@ -71,7 +71,7 @@ if(HAS_CPP11)
     foreach(example
         broker)
       add_executable(mt_${example} mt/${example}.cpp ${container_src})
-      target_link_libraries(mt_${example} pthread)
+      target_link_libraries(mt_${example} pthread atomic)
     endforeach()
     add_cpp_test(cpp_mt_example_test ${PYTHON_EXECUTABLE} ${CMAKE_CURRENT_SOURCE_DIR}/example_test.py -v MtBrokerTest)
   endif()

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: qpid-proton
Source-Version: 0.14.0-5.1

We believe that the bug you reported is fixed in the latest version of
qpid-proton, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <[email protected]> (supplier of updated qpid-proton package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 01 Jul 2017 08:46:28 +0300
Source: qpid-proton
Binary: libqpid-proton8 libqpid-proton-cpp8 libqpid-proton8-dev 
libqpid-proton-cpp8-dev libqpid-proton8-dev-examples libqpid-proton8-dev-doc 
libqpid-proton-cpp8-dev-doc python-qpid-proton python3-qpid-proton 
python-qpid-proton-doc
Architecture: source
Version: 0.14.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Middleware Maintainers 
<[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Description:
 libqpid-proton-cpp8 - C++ libraries for Qpid Proton
 libqpid-proton-cpp8-dev - C++ Development libraries for writing messaging apps 
with Qpid Pr
 libqpid-proton-cpp8-dev-doc - C++ developer documentation for Qpid Proton
 libqpid-proton8 - C libraries for Qpid Proton
 libqpid-proton8-dev - C Development libraries for writing messaging apps with 
Qpid Prot
 libqpid-proton8-dev-doc - Developer documentation for Qpid Proton
 libqpid-proton8-dev-examples - Example applications for writign messaging apps 
with Qpid Proton
 python-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 2.
 python-qpid-proton-doc - Documentation for the Python language bindings for 
Qpid Proton
 python3-qpid-proton - language bindings for Qpid Proton messaging framework - 
Python 3.
Closes: 847976
Changes:
 qpid-proton (0.14.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from James Cowgill to fix FTBFS on mips and mipsel.
     (Closes: #847976)
Checksums-Sha1:
 9684278652330b00f2c24117fbdd178c3dedcf88 2972 qpid-proton_0.14.0-5.1.dsc
 0da780a9df6d4a384f0afacd41fabb0d47940d0f 8776 
qpid-proton_0.14.0-5.1.debian.tar.xz
Checksums-Sha256:
 ae0dce525bfaada744698bc79cdd9781e2b0f69029f2a15b53295b6105ff67a5 2972 
qpid-proton_0.14.0-5.1.dsc
 6d9476cda8e4d86a44a611d5fecb040ba1939eb16f83441460bb7ea96144169c 8776 
qpid-proton_0.14.0-5.1.debian.tar.xz
Files:
 7d36c9201d8eab8c1749e4c03067443c 2972 libs optional qpid-proton_0.14.0-5.1.dsc
 056127974875c6f5b19b5b59948e3f9f 8776 libs optional 
qpid-proton_0.14.0-5.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAllXOE0ACgkQiNJCh6LY
mLFrCw//VUM71mK/bgGhre9Bl1s/1Cx2BwBXyTX8PBMkLC6jZ/2f9eqdpaxb7sr0
+8RE272rI3fgVKxSrKJUm/dDZQv+7sMSOcf4YIw6vdwryaEErmVk0CnB3TFEVQJ2
QhTLfL8F7MCbbequ6S5/BKowK2AjG2Zf63gct71EdmFFbOsJjsM3MHBlUOi0ezd/
H7ENoJIcCRe1CVoFurDntdokkQbW6X/xIbGVcsxanzzRGTz1ic+xdo9oa/mVa+eb
UbJjVxhJefB70+kkFJNPPQXj3T9QgJ6NvVEmMbUzGt3ww999uQtjhyyvHfeVaxxe
UJnXtuDx/WpNPTjbNx+IgcKhDsPIjBp7uXzOKAsEJe6j2itXGiVmyhJCGRM/iYuB
sZmGdhNSoTACLVJWonHhnu5nEnyVCV2dYStvQpIWZn3GFYGCGSNR/d1/O6vJgWbU
qH5dZnphu8mkIlG6P2vQfmBa/SkgncHI8HHrWxQg27ksHQAlf39LJns9qAF2yxon
In9WecoX7HCI3cDIx2KdThVPqFC059pPS+ikzejl4R7zxbAuvhkCmVpaKDRxnlNa
UvtIUoHEO97Zb+WP2OQjfHMNdxe6MXPVk8Jas/gwfOoh+YNJEUdxpt2ARVFH0gqi
GQg4QGdGpKQWk0dLYtMw428MnpLobJuS3JtIBIVhE9Nj6Y6nsjQ=
=xLzd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to