found 735629 1.0.3-1 clone 735629 -1 retitle 735629 yrmcds: FTBFS with GCC 4.6: unrecognized option '-std=gnu++11' retitle -1 yrmcds: FTBFS on powerpc: undefined reference to `atomic_*_8' thanks
u...@debian.org (Aaron M. Ucko) writes: > Great, thanks! GCC 4.8 is now the default on powerpc[1], so that formal > suggestion should be perfectly sufficient. Oops, the g++ metapackage has an epoch, so the requirement actually needs to be g++ (>= 4:4.7); sorry for missing that earlier. That's no longer an issue on powerpc thanks to yesterday's gcc-defaults upload, but ia64 and sparc are another matter. As for powerpc, new errors are now showing up: ./libyrmcds.a(server.o): In function `std::__atomic_base<unsigned long long>::load(std::memory_order) const': /usr/include/c++/4.8/bits/atomic_base.h:496: undefined reference to `__atomic_load_8' ./libyrmcds.a(server.o): In function `std::__atomic_base<unsigned long long>::store(unsigned long long, std::memory_order)': /usr/include/c++/4.8/bits/atomic_base.h:474: undefined reference to `__atomic_store_8' ./libyrmcds.a(sockets.o): In function `std::__atomic_base<unsigned long long>::fetch_add(unsigned long long, std::memory_order)': /usr/include/c++/4.8/bits/atomic_base.h:614: undefined reference to `__atomic_fetch_add_8' It looks like GCC doesn't support atomic operations on 64-bit (8-byte) types on 32-bit powerpc; I suspect that's an inherent limitation, but am noting the errors for the record. In general, you can find build logs at https://buildd.debian.org/status/package.php?p=yrmcds . -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
