March 2009 - Boost - lists.preview.boost.org

[interprocess] locked mutex and process killed
by vicente.botet 25 Mar '09

25 Mar '09

Hi, what happens when a process owning interprocess::mutex is killed? is the mutex unlocked before the process dies? Thanks, Vicente

6 13

A problem of Regex with ICU support
by Qihong Wang 25 Mar '09

25 Mar '09

Hi, I build my regex with icu support on Linux machine as follows ./bjam --prefix=/home/qhwang/mylibs/boost/ --with-regex --build-dir=/tmp/boost_build/ --build-type=complete -sHAVE_ICU=1 -sICU_PATH=/home/qhwang/mylibs/icu/ install The warning message from bjam shows icu is enabled. I checked regex libraies were built. They are dependend on icu library. So I believed HAVE_ICU took effect. But look at the regex head files created, #define BOOST_HAS_ICU is comment. Sounds like icu is not enabled in head files. I compiled icu_example from boost.regex source code mannually, with the BOOST_HAS_ICU enable. g++ -L/home/qhwang/mylibs/boost/lib/ -L/home/qhwang/mylibs/icu/lib/ -I/home/qhwang/mylibs/boost/include/boost-1_38 -I/home/qhwang/mylibs/icu/include -DBOOST_HAS_ICU -lboost_regex-gcc41-mt -licudata -licuuc -licui18n -o icu_example icu_example.cpp The compiler reported error when compile UnicodeString text = L"Some where in \x0391\x039D\x0395\x0398\x0391 2004"; and assert(greek == L"\x0391\x039D\x0395\x0398\x0391 2004"); The error messages are: In function âint main()â: icu_example.cpp:155: error: conversion from âconst wchar_t [25]â to âicu_4_0::UnicodeStringâ is ambiguous /home/qhwang/mylibs/icu/include/unicode/unistr.h:2695: note: candidates are: icu_4_0::UnicodeString::UnicodeString(UChar32) <near match> /home/qhwang/mylibs/icu/include/unicode/unistr.h:2688: note: icu_4_0::UnicodeString::UnicodeString(UChar) <near match> icu_example.cpp:157: error: conversion from âconst wchar_t [11]â to âconst icu_4_0::UnicodeStringâ is ambiguous I don't know how to pass the compiliation. Any idea? Thanks, Qihong

2 1

Stop on first error
by Vladimir Prus 25 Mar '09

25 Mar '09

Presently, when building Boost, the build process does not stop if an error has occurred. This is behaviour we inherited, and it differs from every other build system out there. We had quite a number of users confused where build ends with "failed N targets", with the original error scrolled away -- it is not apparent what has caused the error, and often, the error is not even available from console program history. While experienced users might prefer being able to kick a build, go to lunch, and then fix a couple of failures in the middle of the build, ordinary users don't like it so much. So, how about we do what the rest of the world does, and stop build of C++ Boost on the first error? Comments? - Volodya

14 15

BoostCon 2009 Schedule Now Live
by David Abrahams 24 Mar '09

24 Mar '09

The official schedule is now live at http://www.boostcon.com/program! A few highlights of the "mouth-watering content" (in the words of one enrollee) are: * A keynote address from Andrei Alexandrescu called "Iterators Must Go." It's sure to be provocative! * Troy Straszheim's presentations on how high-energy physicists are using Boost to process massive datasets as they go "Icefishing for Neutrinos" and on Kamasu, his library for offloading computation to your machine's GPU. * Two hands-on sessions where we'll start recoding parts of Boost for C++0x, applying rvalue references, variadic templates, decltype, and advanced SFINAE capabilities using the latest GCC. * "Practical C++ Test-Driven Development with Boost.Test and Bmock," by Asher Sterkin * A session on compiler construction using Boost.Spirit v2, from Hartmut Kaiser and Joel de Guzman The complete list of sessions covers a wide range of other Boost and C++-related topics. It is available at http://www.boostcon.com/program/sessions. Please have a look, and please, sign up for the conference! Remember, registration for the whole week is just $599 before April 1st. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

[tr1] shared_count failing on several release branch tests
by Beman Dawes 24 Mar '09

24 Mar '09

shared_count is also failing more-or-less across the board on the trunk tests. Could someone (John M?) please take a look at this test? Thanks, --Beman

2 1

basic_timed_mutex.hpp Assertion failed. Bug not fixed in Boost 1.38?
by Filip Klasson 24 Mar '09

24 Mar '09

Hi, I get Assertion failed timed_lock(::boost::detail::get_system_time_sentinel()), file c:\boost\thread\win32\basic_timed_mutex.hpp, line 64. Code in basic_timed_mutex.hpp: void lock() { BOOST_VERIFY(timed_lock(::boost::detail::get_system_time_sentinel())); //Line 64 } I read in a previous thread that this was a known bug that is fixed in Boost 1.38 but i am using Boost 1.38. Is this another bug or is it not fixed? This only happends sometimes and it happends when i call wait on a condition variable. Here is my code, i have marked where Assertion failed happends. boost::mutex::scoped_lock lock(_mutex); while(_queue.empty()) { _condition.wait(lock); } //Assertion failed happends here. //Another thread is signaling the condition variable when an element is added to the _queue. I am happy with all sorts of helpful comments. Best regards

1 0

Boost with ICU on AIX - Patch
by solar＠rootdirectory.de 24 Mar '09

24 Mar '09

Hi there, while trying to get Boost 1.34.1 to work on an AIX machine, I found a bug that still persists in 1.38.0. You might want to fix this... In boost/regex/icu.hpp: 314c314 < typedef std::vector<UCHAR32> vector_type; --- > typedef std::vector<UChar32> vector_type; 318,319c318,319 < v.push_back((UCHAR32)(*i)); < ++a; --- > v.push_back((UChar32)(*i)); > ++i; It should be obvious once you look at the source environment - the UCHAR32 is probably a typo, and the ++a is copy-and-paste work. This has obviously never been test-compiled on a real machine. Surprising that this has not been caught earlier (since it's been in there since 1.33)... Anyway, with that patch (and a backport of another one on vacpp.jam that's been included in later versions of Boost), v1.34.1 compiles cleanly with ICU-support on AIX. Regards, Martin Baute

2 1

"[gsoc] Thread scheduler support for boost"
by Indradip Ghosh 23 Mar '09

23 Mar '09

Hi , I would like to get suggestions on developing a thread scheduler API for supporting users having specific needs in prioritizing threads running on SMP / Multi-Core processors. Please let me know the viability of including such an API in generic boost distribution and whether anyone would volunteer to mentor this effort as a GSOC project. BR, Indradip.

3 2

How to build 32 bits boost library on a 64 bits platform
by Qihong Wang 23 Mar '09

23 Mar '09

Hello, My platform is a 64 bits Linux with gcc. My program needs to link a 32 bits library without source code and other libraries with source code. I wrote a script to build those libraries with source code by ./configure --prefix=$install_prefix CFLAGS="-g -O2 -Wall -m32" CPPFLAGS=-m32 CXXFLAGS="-g -O2 -m32" make install Then start to build my executable through Makefile with -m32 flag either. The configure and make install work for other libraries but not work for boost. The boost libraries were compiled and installed but still 64 bits. Linker refused to link it. Is there any simple approach to build 32 bits boost on 64 bits Linux? Thanks, Qihong

3 3

[GSOC] 10 Day student application period begins today
by troy d. straszheim 23 Mar '09

23 Mar '09

The window is open another week and a half or so. Deadline: April 3. Our first student proposal (py3k support for boost python) arrived within moments of the start of the application period. Don't be shy, keep discussing your ideas, and make some proposals. You can't get accepted if you don't apply. -t

1 0