September 2012 - Boost-users - lists.preview.boost.org

How to compile static library with -fPIC from boost.python
by simon zhang 15 Sep '12

15 Sep '12

Hi all Default,libboostpython.a has be compiled without -fPIC.But I have to make a python extending and it is a dynamic library with -fPIC that link to static library. How to compile static library (libboostpython.a) with -fPIC from boost.python simon

2 2

std::set_intersection without results
by Jens Müller 14 Sep '12

14 Sep '12

Hi everyone, I'm trying to test whether two std::vector's intersect. A straightforward way is to sort them, apply std::set_intersection and test whether the result set is non-empty. However, I don't need the result. Is there some algorithm in boost that just _tests_ for intersection, i.e., stops when it has found one common element? Best regards, Jens

2 1

[filesystem] boost::filesystem::current_path: No such file or directory
by Frédéric Bron 14 Sep '12

14 Sep '12

Hi, sometimes, when I run my program, I get that exception: terminate called after throwing an instance of 'boost::filesystem3::filesystem_error' what(): boost::filesystem::current_path: No such file or directory Aborted What could be the cause for this? I am using 1.49.0 on linux x86_64 compiled with g++ 4.6.2. Regards, Frédéric

4 5

[lambda] Using a reference in an expression
by Bill Buklis 13 Sep '12

13 Sep '12

How does one use a reference in a lambda expression? The documentation says that "var" does, but it clearly doesn't. For example this fails to compile because it can't access the copy constructor: #include <boost/lambda.hpp> namespace bll = boost::lambda; class sample { public: sample() { } sample& operator<<( int ) { return(*this); } private: sample( const sample& ); }; void test() { typedef std::vector<int> V; V v; sample s; std::for_each(v.begin(), v.end(), bll::var(s) << bll::_1); }; -- Bill

2 2

[scope exit] docs broken in 1.50
by Ovanes Markarian 13 Sep '12

13 Sep '12

2 3

Install boost on OS X via homebrew with c++11 and libc++
by christoffer.buchholz＠gmail.com 13 Sep '12

13 Sep '12

I'm trying to install boost on OS X with c++11 and libc++. I'm using homebrew (boost formular with the --build-from-source argument) and have tried various options with adding stuff like * toolset=clang * cxxflags="-stdlib=libc++ -std=c++11" * cxxflags="-stdlib=libc++" * linkflags="-stdlib=libc++ -std=c++11" * linkflags="-stdlib=libc++" as arguments to bjam, but it all fails. Now... The "toolset" part doesn't do anything to make it fail though, its the cxx- and linkflags part that does. This is what I get when it fails clang-darwin.archive bin.v2/libs/exception/build/clang-darwin-4.2.1/release/link- static/threading-multi/libboost_exception-mt.a common.copy /usr/local/Cellar/boost/1.50.0/lib/libboost_exception-mt.a clang-darwin.compile.c++ bin.v2/libs/wave/build/clang-darwin-4.2.1/release/link- static/threading-multi/cpplexer/re2clex/cpp_re.o clang-darwin.archive bin.v2/libs/wave/build/clang-darwin-4.2.1/release/link-static/threading-multi/libboost_wave-mt.a common.copy /usr/local/Cellar/boost/1.50.0/lib/libboost_wave-mt.a ...failed updating 2 targets... ...skipped 4 targets... ...updated 10592 targets... Error: #<BuildError: Failed executing: ./bjam toolset=clang cxxflags="-stdlib=libc++" linkflags="-stdlib=libc++" --prefix=/usr/local/Cellar/boost/1.50.0 -- libdir=/usr/local/Cellar/boost/1.50.0/lib -j2 --layout=tagged --user-config=user-config.jam threading=multi install> How do I get boost installed on OS X Mountain Lion with c++11 and libc++ preferably via homebrew for the ease it adds. Sincerely, Christoffer Buchholz

2 3

[test] BOOST_CHECK_EQUAL comparisons with NULL don't compile
by James Mathiesen 13 Sep '12

13 Sep '12

This use case seems really common and I was surprised it gave me problems. I assume that nullptr_t in C++11 fixes this but then I was wondering if the cases were basic and common enough it would make sense to have a BOOST_CHECK_NULL / BOOST_CHECK_NOT_NULL and the assorted variants. james --- #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MODULE Hello #include <boost/test/unit_test.hpp> // main() etc... is defined by the headers BOOST_AUTO_TEST_CASE( null_compare ) { const char *ptr = NULL; // // Equality comparisons with NULL Fail to compile using boost 1.46 // and g++-4.6 // // /usr/include/boost/test/test_tools.hpp:536:20: // error: ISO C++ forbids comparison between pointer and // integer [-fpermissive] // // Which seems to be flagging this // // template <class Left, class Right> // predicate_result equal_impl( Left const& left, Right const& right ) // { // return left == right; // } // // Where Left is of type "const char *" and Right is of type "long int". // BOOST_CHECK_EQUAL(ptr, NULL); // // these tests compile and pass // BOOST_CHECK(ptr == NULL); BOOST_CHECK_EQUAL(ptr, ptr); BOOST_CHECK_EQUAL(ptr, (void *)ptr); BOOST_CHECK_EQUAL(ptr, (void *)NULL); } ... example.cc:33:1: error: passing NULL to non-pointer argument 9 of ‘bool boost::test_tools::tt_detail::check_frwd(Pred, const boost::unit_test::lazy_ostream&, boost::test_tools::const_string, std::size_t, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, const Arg0&, const char*, const Arg1&, const char*) [with Pred = boost::test_tools::tt_detail::equal_impl_frwd, Arg0 = const char*, Arg1 = long int, boost::test_tools::const_string = boost::unit_test::basic_cstring<const char>, std::size_t = long unsigned int]’ [-Werror=conversion-null] example.cc:33:1: error: passing NULL to non-pointer argument 9 of ‘bool boost::test_tools::tt_detail::check_frwd(Pred, const boost::unit_test::lazy_ostream&, boost::test_tools::const_string, std::size_t, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, const Arg0&, const char*, const Arg1&, const char*) [with Pred = boost::test_tools::tt_detail::equal_impl_frwd, Arg0 = const char*, Arg1 = long int, boost::test_tools::const_string = boost::unit_test::basic_cstring<const char>, std::size_t = long unsigned int]’ [-Werror=conversion-null] In file included from /usr/include/boost/test/unit_test.hpp:19:0, from example.cc:7: /usr/include/boost/test/test_tools.hpp: In function ‘boost::test_tools::predicate_result boost::test_tools::tt_detail::equal_impl(const Left&, const Right&) [with Left = const char*, Right = long int]’: /usr/include/boost/test/test_tools.hpp:560:40: instantiated from ‘boost::test_tools::predicate_result boost::test_tools::tt_detail::equal_impl_frwd::call_impl(const Left&, const Right&, mpl_::false_) const [with Left = const char*, Right = long int, mpl_::false_ = mpl_::bool_<false>]’ /usr/include/boost/test/test_tools.hpp:575:56: instantiated from ‘boost::test_tools::predicate_result boost::test_tools::tt_detail::equal_impl_frwd::operator()(const Left&, const Right&) const [with Left = const char*, Right = long int]’ /usr/include/boost/test/test_tools.hpp:523:1: instantiated from ‘bool boost::test_tools::tt_detail::check_frwd(Pred, const boost::unit_test::lazy_ostream&, boost::test_tools::const_string, std::size_t, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, const Arg0&, const char*, const Arg1&, const char*) [with Pred = boost::test_tools::tt_detail::equal_impl_frwd, Arg0 = const char*, Arg1 = long int, boost::test_tools::const_string = boost::unit_test::basic_cstring<const char>, std::size_t = long unsigned int]’ example.cc:33:1: instantiated from here /usr/include/boost/test/test_tools.hpp:536:20: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]

4 3

boost 1.47.0 installation
by Usman Dastgeer 13 Sep '12

13 Sep '12

Hello, I am trying to install boost for the first time as part of rose compiler installation. Here is what I did on a Linux machine: downloaded, extracted boost 1.47.0 ./bootstrap.sh --prefix=/home/usmda/rose/ boost/install2 --with-python-version=2.7 ./bjam install -sGCC=gcc-4.4 -sGXX=g++-4.4 --prefix=/home/usmda/rose/boost/install2 Default gcc version is 4.7.1 [/usr/bin/g(cc|++)] on this machine so I specify the gcc 4.4 [/usr/bin/g(cc|++)-4.4] for 2 reasons: 1) I need to use gcc 4.4 to compile rose compiler as well. 2) I read that gcc 4.7.1 disables boost threading support so that's why I want to use gcc 4.4 but specifying -sGCC and -sGXX didn't help as still I guess it uses gcc-4.7.1 (as shown in log below).* * Build fail for 4 targets. Here is the build message... ... In file included from ./boost/thread/detail/platform.hpp:17:0, from ./boost/thread/detail/config.hpp:20, from libs/thread/src/pthread/thread.cpp:8: ./boost/config/requires_threads.hpp:29:4: error: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" In file included from ./boost/thread/pthread/mutex.hpp:14:0, from ./boost/thread/mutex.hpp:16, from ./boost/thread/pthread/thread_data.hpp:12, from ./boost/thread/thread.hpp:17, from libs/thread/src/pthread/thread.cpp:10: ./boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant ./boost/thread/xtime.hpp:23:5: error: expected ‘}’ before numeric constant ./boost/thread/xtime.hpp:23:5: error: expected unqualified-id before numeric constant ./boost/thread/xtime.hpp:46:14: error: expected type-specifier before ‘system_time’ In file included from ./boost/thread/pthread/mutex.hpp:14:0, from ./boost/thread/mutex.hpp:16, from ./boost/thread/pthread/thread_data.hpp:12, from ./boost/thread/thread.hpp:17, from libs/thread/src/pthread/thread.cpp:10: ./boost/thread/xtime.hpp: In function ‘int xtime_get(xtime*, int)’: ./boost/thread/xtime.hpp:73:40: error: ‘get_system_time’ was not declared in this scope ./boost/thread/xtime.hpp:73:40: note: suggested alternative: In file included from ./boost/thread/locks.hpp:12:0, from ./boost/thread/pthread/mutex.hpp:12, from ./boost/thread/mutex.hpp:16, from ./boost/thread/pthread/thread_data.hpp:12, from ./boost/thread/thread.hpp:17, from libs/thread/src/pthread/thread.cpp:10: ./boost/thread/thread_time.hpp:19:24: note: ‘boost::get_system_time’ In file included from ./boost/thread/pthread/mutex.hpp:14:0, from ./boost/thread/mutex.hpp:16, from ./boost/thread/pthread/thread_data.hpp:12, from ./boost/thread/thread.hpp:17, from libs/thread/src/pthread/thread.cpp:10: ./boost/thread/xtime.hpp: At global scope: ./boost/thread/xtime.hpp:88:1: error: expected declaration before ‘}’ token "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -Wno-long-long -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DNDEBUG -I"." -c -o "bin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi/pthread/thread.o" "libs/thread/src/pthread/thread.cpp" ...failed gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi/pthread/thread.o... gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi/pthread/once.o In file included from ./boost/thread/detail/platform.hpp:17:0, from ./boost/thread/once.hpp:12, from libs/thread/src/pthread/once.cpp:7: ./boost/config/requires_threads.hpp:29:4: error: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -Wno-long-long -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DNDEBUG -I"." -c -o "bin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi/pthread/once.o" "libs/thread/src/pthread/once.cpp" ...failed gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi/pthread/once.o... ...skipped <pbin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi>libboost_thread.a(clean) for lack of <pbin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi>pthread/thread.o... ...skipped <pbin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi>libboost_thread.a for lack of <pbin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi>pthread/thread.o... ...skipped <p/home/usmda/rose/boost/install2/lib>libboost_thread.a for lack of <pbin.v2/libs/thread/build/gcc-4.7.1/release/link-static/threading-multi>libboost_thread.a... gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_cpp_exprgrammar.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_cpp_grammar.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_cpp_literalgrs.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_defined_grammar.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_predef_macros.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_re2c_lexer.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/instantiate_re2c_lexer_str.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/token_ids.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/wave_config_constant.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/cpplexer/re2clex/aq.o gcc.compile.c++ bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/cpplexer/re2clex/cpp_re.o gcc.archive bin.v2/libs/wave/build/gcc-4.7.1/release/link-static/threading-multi/libboost_wave.a common.copy /home/usmda/rose/boost/install2/lib/libboost_wave.a ...failed updating 4 targets... ...skipped 9 targets... ...updated 9270 targets...

2 1

[Interprocess] Growing resets permissions
by Aaron_Wright＠selinc.com 12 Sep '12

12 Sep '12

I have a situation where I don't know how much shared memory I need, so I made the shared memory grow when it ran out of space. My shared memory is shared between a process running as root and postgres, which won't run as root. So I set the permissions to unrestricted (0666) when I create the shared memory. My problem is that when I grow the shared memory, the permissions are reset to (0644). This breaks things, as postgres can no longer open the shared memory for writing. I followed the code a bit and saw that it was using ftruncate. Checking the man page for ftruncate reveals, "the set-user-ID and set-group-ID permission bits may be cleared." Has anyone else ran into this? What is the easy solution? Should I just set the permissions manually after growing? Is this a bug in the interprocess library? --- Aaron Wright

2 1

FW: [Review] Coroutine review starts today, September 3rd, ends September 12th
by Hartmut Kaiser 11 Sep '12

11 Sep '12

This is just a reminder that the review of Oliver's Boost.Coroutine is ending tomorrow (see below for the initial announcement). Please get your reviews in as soon as possible. If you need more time, please let me know. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > -----Original Message----- > From: Hartmut Kaiser [mailto:hartmut.kaiser@gmail.com] > Sent: Monday, September 03, 2012 6:46 AM > To: boost-users(a)lists.boost.org > Subject: {Review] Coroutine reviewstarts today, September 3rd > > > Hi all, > > The review of Oliver Kowalke's Boost.Coroutine library starts today, > September 3rd 2012, and will end on September 12th. > I really hope to see your vote and your participation in the discussions > on the Boost mailing lists! > > ----------------------------------------------------- > > About the library: > > Boost.Coroutine provides templates for generalized subroutines > (coroutines) which allow multiple entry points for suspending and resuming > execution at certain locations. It preserves local state/data and allows > re-entering subroutines more than once (useful if state must be kept > across function calls). Coroutines can be viewed as a language-level > construct providing a special kind of control flow. > > You can download the library and the view documentation here: > > docs: http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/ > src: http://ok73.ok.funpic.de/boost.coroutine.zip > > --------------------------------------------------- > > Please always state in your review, whether you think the library should > be accepted as a Boost library! > > Additionally please consider giving feedback on the following general > topics: > > - What is your evaluation of the design? > - What is your evaluation of the implementation? > - What is your evaluation of the documentation? > - What is your evaluation of the potential usefulness of the library? > - Did you try to use the library? With what compiler? Did you have any > problems? > - How much effort did you put into your evaluation? A glance? A quick > reading? In-depth study? > - Are you knowledgeable about the problem domain? > > Regards Hartmut > Review Manager

1 0