|
Boost Testing : |
Subject: Re: [Boost-testing] [minion-release-clang-libcxx] try_lock acceisble without namespace qualification
From: Christopher Jefferson (chris_at_[hidden])
Date: 2012-01-02 17:43:35
I will do, but it will not happen for a week or so. As we shut down various systems for Christmas.
Chris
On 2 Jan 2012, at 21:46, Vicente J. Botet Escriba wrote:
>
> The following tester is reporting an strange error as if the standard try_lock was unscoped or if a hyden using std.
>
> Please could you provide the output of the preprocessor on this tester for the concerned test?
>
> Best,
> Vicente
>
> Test output: minion-release-clang-libcxx - thread - test_generic_locks / clang-darwin-libcxx
> Rev 75447 / Fri, 11 Nov 2011 23:55:19 +0000
> *Report Time: *Mon, 2 Jan 2012 08:02:52 +0000
> Compile [2011-11-12 05:05:42 UTC]: fail
> "/llvm-bin/bin/clang++" -x c++ -O0 -g -O0 -fno-inline -Wall -g -stdlib=libc++ -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_NO_AUTO_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -I".." -c -o "/Users/caj/llvmboosttest/boost-build-clang-libcxx/results/boost/bin.v2/libs/thread/test/test_generic_locks.test/clang-darwin-libcxx/debug/threading-multi/test_generic_locks.o""../libs/thread/test/test_generic_locks.cpp"
> In file included from ../libs/thread/test/test_generic_locks.cpp:7:
> In file included from ../boost/thread/mutex.hpp:16:
> In file included from ../boost/thread/pthread/mutex.hpp:12:
> ../boost/thread/locks.hpp:1546:48: error: call to 'try_lock' is ambiguous
> Iterator const failed_lock=try_lock(next,end);
> ^~~~~~~~
> ../boost/thread/locks.hpp:1288:9: note: in instantiation of function template specialization 'boost::detail::lock_impl<dummy_iterator>' requested here
> detail::lock_impl(m1,m2,detail::is_mutex_type_wrapper<is_mutex_type<MutexType1>::value>());
> ^
> ../libs/thread/test/test_generic_locks.cpp:356:5: note: in instantiation of function template specialization 'boost::lock<dummy_iterator, dummy_iterator>' requested here
> boost::lock(dummy_iterator(mutexes),dummy_iterator(mutexes+num_mutexes));
> ^
> /usr/include/c++/v1/mutex:305:1: note: candidate function [with _L0 = dummy_iterator, _L1 = dummy_iterator]
> try_lock(_L0& __l0, _L1& __l1)
> ^
> ../boost/thread/locks.hpp:1428:61: note: candidate function [with MutexType1 = dummy_iterator, MutexType2 = dummy_iterator]
> typename detail::try_lock_impl_return<MutexType1>::type try_lock(MutexType1& m1,MutexType2& m2)
> ^
> ../boost/thread/locks.hpp:1434:61: note: candidate function [with MutexType1 = dummy_iterator, MutexType2 = dummy_iterator]
> typename detail::try_lock_impl_return<MutexType1>::type try_lock(const MutexType1& m1,MutexType2& m2)
> ^
> ../boost/thread/locks.hpp:1440:61: note: candidate function [with MutexType1 = dummy_iterator, MutexType2 = dummy_iterator]
> typename detail::try_lock_impl_return<MutexType1>::type try_lock(MutexType1& m1,const MutexType2& m2)
> ^
> ../boost/thread/locks.hpp:1446:61: note: candidate function [with MutexType1 = dummy_iterator, MutexType2 = dummy_iterator]
> typename detail::try_lock_impl_return<MutexType1>::type try_lock(const MutexType1& m1,const MutexType2& m2)
> ^
> 1 error generated.
>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing