Processing commands for [email protected]: > reopen 721577 Bug #721577 {Done: [email protected] (Steve M. Robbins)} [libboost-thread1.54.0] libboost-thread1.54.0: should link against Boost.Atomics on some architectures Bug #721544 {Done: [email protected] (Steve M. Robbins)} [libboost-thread1.54.0] performous: FTBFS on ia64, mips(el), s390(x): /usr/lib/gcc/ia64-linux-gnu/4.6/../../../libboost_thread.so: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)' 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions boost1.54/1.54.0-3. No longer marked as fixed in versions boost1.54/1.54.0-3. > affects 721577 src:cpp-netlib Bug #721577 [libboost-thread1.54.0] libboost-thread1.54.0: should link against Boost.Atomics on some architectures Bug #721544 [libboost-thread1.54.0] performous: FTBFS on ia64, mips(el), s390(x): /usr/lib/gcc/ia64-linux-gnu/4.6/../../../libboost_thread.so: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)' Added indication that 721577 affects src:cpp-netlib Added indication that 721544 affects src:cpp-netlib > found 721577 boost1.54/1.54.0-3 Bug #721577 [libboost-thread1.54.0] libboost-thread1.54.0: should link against Boost.Atomics on some architectures Bug #721544 [libboost-thread1.54.0] performous: FTBFS on ia64, mips(el), s390(x): /usr/lib/gcc/ia64-linux-gnu/4.6/../../../libboost_thread.so: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)' Marked as found in versions boost1.54/1.54.0-3. Marked as found in versions boost1.54/1.54.0-3. > thanks Stopping processing here.
Please contact me if you need assistance. -- 721544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721544 721577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721577 Debian Bug Tracking System Contact [email protected] with problems -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
