February 2011 - Boost-users

cannot find config script in Boost 1.45.0_1 mac os x (snow), g++ 4.2.1
by ny 23 Feb '11

23 Feb '11

Hi, I wonder if my boost set-up is the "proper" one since I cannot find config script as described in here http://goo.gl/yPe9V Any ideas? Nikos Yiotis Chat Skype: nyiotis Contact Me [image: Linkedin]<http://my.wisestamp.com/link?u=ws7c27w2vnrx4d2b&site=www.linkedin.com/in/yi…>

3 5

Boost release 1.46.0 available
by Beman Dawes 23 Feb '11

23 Feb '11

Release 1.46.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release includes 1 new library (Interval Container Library) as well as updates to many existing libraries. For details, including download links, see http://www.boost.org/users/news/version_1_46_0 The release can also be downloaded directly from SourceForge. See http://sourceforge.net/projects/boost/files/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team

2 1

Re: [Boost-users] [boost] Boost release 1.46.0 available
by Daniel James 23 Feb '11

23 Feb '11

On 22 February 2011 15:33, Vladimir Prus <vladimir(a)codesourcery.com> wrote: > > It's not. I suggest any links to bjam be removed. OK, I'll remove the link on the home page soon. >> then it probably also means that the build and jam >> documentation on the site are out of date. > > At which URL specifically? I think all documentation for Boost.Build > is up to date. Also, there should be no documentation for Boost.Jam now. http://www.boost.org/tools/jam/ l can change it to redirect to the relevant part of the build documentation, although that's moved around a bit recently so it's hard to keep up. Daniel

2 3

[Filesystem] Symbol not found: boost::filesystem2::detail::status_api
by Nicolas Chaumont 23 Feb '11

23 Feb '11

Hello and thank you for reign my post, When I want to compile the program: #include "boost/filesystem.hpp" int main(int argc, char** argv) { boost::filesystem::path path; boost::filesystem::exists(path); //<=This is the line that causes the error return 0; } I get the following error: "boost::filesystem2::detail::status_api(std::basic_string<char, std::char_traits <char>, std::allocator<char> > const&, boost::system::error_code&)", referenced from: boost::enable_if<boost::filesystem2::is_basic_path<boost::filesystem2::basic_pat h<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem2::path_traits> >, bool>::type boost::filesystem2::exists< boost::filesystem2::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem2::path_traits> >( boost::filesystem2::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem2::path_traits> const&)in main.o ld: symbol(s) not found collect2: ld returned 1 exit status I'm using XCode 3.2.4, Darwin GCC 4.2 with the Mac OSX 10.6 SDK. The program links against the libboost_system.a and libboost_filesystem.a libraries from Boost 1.45, both compiled with the same compiler. Boost was compiled in the most straight forward way, i.e. from the boost root directory, I invoke the only two commands: ./bootstrap.sh make Note that I haven't installed the library in /usr/local. Since the example compiles fine with the problematic line commented out, I assume the include path is correct, and that the linker found libboost_system.a (in stage/lib). I also made sure there are no other versions of boost present on my computer to eliminate the possibility of a header/library version mismatch. Also, I've tried to compile with different architectures, both in debug and release mode. I couldn't remove this error. I looked for the missing symbol in both libboost_system.a and libboost_filesystem.a (nm -m <library name> | c++filt), and the filesystem2 namespace doesn't exist. My understanding is that the boost::filesystem2 namespace was never generated when I compiled the libraries, but for some reason is generated when I compile my little program. So I suppose there might be a definition that triggers or prevents this namespace from being created. Anyone has an idea about what should I do to remove my error? Thank you in advance, Regards, Nicolas

2 1

boost::transform_iterator and C++0x decltype
by Nathan Ridge 23 Feb '11

23 Feb '11

Hello, Currently (boost 1.46) boost::transform_iterator requires that the unary functor 'f' passed to it use the 'result_of' protocol to declare its return type (that is, it must either have a nested 'result_type' typedef, or in the case of polymorphic functions, a nested 'result' metafunction that computes the return type given the parameter type). Would it be a good idea to modify the requirements so that if the boost library detects C++0x support, it uses 'decltype' to determine the return type of the functor, so that the functor does not have to use the 'result_of' protocol? I would be happy to contribute a patch implementing this. Regards, Nate.

2 1

[spirit] how to write parser for matching character not in list ?
by Kamil Zubair 23 Feb '11

23 Feb '11

Let's say I want to match a string and that string cannot contain character ; and @. How to write parser for that ? I try using: *(!(';"'|'@')) and *(char_ - ';'|'@') but both are failed to compile. Thanks.

2 1

Build error 1.46
by gast128 23 Feb '11

23 Feb '11

Hello all, I got a build error when building Boost 1.46 on Visual Studio 2003 (MSVC 7.1) in Boost.Fusion: compile-c-c++ bin.v2\libs\math\build\msvc-7.1\debug\pch-off\threading-multi\asso c_legendre.obj assoc_legendre.cpp boost\fusion\sequence\comparison\less_equal.hpp(49) : error C2039: 'is_native_fu sion_sequence' : is not a member of 'boost::fusion::detail' boost\fusion\sequence\comparison\less_equal.hpp(49) : error C2065: 'is_native_fu sion_sequence' : undeclared identifier boost\fusion\sequence\comparison\less_equal.hpp(49) : error C2974: 'boost::disab le_if' : invalid template argument for 'Cond', type expected boost\utility\enable_if.hpp(59) : see declaration of 'boost::disable_if' Anyone?

6 11

issues having upgraded to 1.46
by Sean Farrow 23 Feb '11

23 Feb '11

Hi: Having upgraded and build 1.46, I'm getting the error: 1>LINK : fatal error LNK1104: cannot open file 'libboost_system-vc100-mt-gd-1_45.lib' Can someone tell me where the linking is controlled, I've done a search in the entire boost directory, but carn't find where this could be happening! I'm using the boost.filesystem library, and elements boost::system::error_code from boost.system. Anyone give me some pointers! Cheers Sean.

2 2

Conditions for casting stream_buffer to std::basic_streambuf
by Tyler Weston 22 Feb '11

22 Feb '11

Hi All, How do you construct an std::ostream from a boost::iostreams::stream_buffer<io::back_insert_device<...> > ? Is this not possible with a simple sink_tag for the category? I'm using libpng and want to abstract writing to a file directly or to a memory buffer. libpng provides hooks for write and flush functions, and never seeks. I implemented these functions for std::ostream and it works great for file writing. My assumption that it would be trivial to provide a std::ostream to a memory buffer turned out to be incorrect. Unfortunately type information is lost through libpng as you have to pass your io data as void*, which makes using templatized stream classes difficult. In the tutorial for iostreams it says: "The template io::streamis provided as a convenience. It's always possibly to avoid io::stream and simply use io::stream_buffer together with one of the standard library stream templates." I tried following this pattern, and it works great for files: io::file_sink sink(filename, std::ios_base::out | std::ios_base::trunc | std::ios_base::binary); io::stream_buffer<io::file_sink> streamBuf(sink); std::ostream pngStream(&streamBuf); However, I am having problems providing an ostream for the memory buffer case. shared_ptr<vector<char> > vec(new vector<char>()); io::back_insert_device<vector<char> > sink(*vec); io::stream_buffer<io::back_insert_device<vector<char> > > streamBuf(sink); std::ostream pngStream(&streamBuf); This snippet produces the following error in msvc 9 with boost 1.45. 2>error C2664: 'std::basic_ostream<_Elem,_Traits>::basic_ostream(std::basic_streambuf<_Elem,_Traits> *,bool)' : cannot convert parameter 1 from 'boost::iostreams::stream_buffer<T> *' to 'std::basic_streambuf<_Elem,_Traits> *' 2> with 2> [ 2> _Elem=char, 2> _Traits=std::char_traits<char> 2> ] 2> and 2> [ 2> T=boost::iostreams::back_insert_device<std::vector<char>> 2> ] 2> and 2> [ 2> _Elem=char, 2> _Traits=std::char_traits<char> 2> ] 2> Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast I noticed file_sink::category has more tags than back_insert_device::category, so I took the container_device in the tutorial and implemented all the tags that file_sink has, and still get the same error. Digging farther I see that basic_file::impl contains an actual std::basic_filebuf which can be casted to basic_streambuf. The basic_filebuf is private member of a private member, so shouldn't be accessible for normal casting and I don't see the cast explicitly provided. How does the file_sink to basic_streambuf cast work? How can I implement this cast for container_device without inheriting and overriding all of the methods of basic_streambuf? Is there an abstract parent class to boost::iostreams::stream or stream_buffer that allows for polymorphism to ease the pain of the required void* cast? I'm still relatively new to metaprogramming patterns. As a side note, the tutorial continues to suggest default-constructing a std::ostream, which is not possible at least with msvc's std implementation.

1 0

[Thread] Interrupting a thread causes a segmentation fault
by W Frane 22 Feb '11

22 Feb '11

Hello, I'm new to the Boost libraries and I've been attempting to implement basic multithreading using the Boost Thread library. I'm currently experiencing a problem: when I interrupt a thread my program crashes with a segmentation fault. I've done quite a bit of research on the internet regarding this problem and, although similar problems have been reported before, none of the solutions have worked for me (a number of people have indicated that interrupts work when linking with the static library, just not with the dynamic library, but I was using the static library to begin with). Technical details are: Boost version: 1.45.0 Compiler: MinGW 4.4.1 IDE: Code Blocks 10.05 The build log output from Code Blocks is: mingw32-g++.exe -Wall -fexceptions -g -I"C:\Program Files\boost\boost_1_45_0" -c "C:\Documents and Settings\WFrane\My Documents\C++ code\boost thread interrupt test\boost_thread_interrupt_test\main.cpp" -o obj\Debug\main.o mingw32-g++.exe -L"C:\Program Files\boost\boost_1_45_0\stage\lib" -o bin\Debug\boost_thread_interrupt_test.exe obj\Debug\main.o "C:\Program Files\boost\boost_1_45_0\stage\lib\libboost_thread-mgw44-mt-d-1_45.a" (I've also tried a release build with the appropriate version of the Boost.Thread library and the resulting program experiences the same problem.) I've included a short program below that exhibits this problem. Any suggestions as to what might be causing this and how it could be resolved would be appreciated. Regards, W. Frane EXAMPLE CODE: #define BOOST_THREAD_USE_LIB // This line was necessary to link with the static libraries. #include #include using namespace std; boost::mutex mutexCout; void testingThread(){ try{ while(1){ boost::this_thread::interruption_point(); } } catch(boost::thread_interrupted const& e){ // Thread was interrupted. mutexCout.lock(); cout << "THREAD: Ending." << endl; mutexCout.unlock(); } catch(...){ mutexCout.lock(); cout << "THREAD: Unknown exception." << endl; mutexCout.unlock(); } } int main(int argc, char* argv[]) { boost::thread testThread(testingThread); mutexCout.lock(); cout << "MAIN: Created thread; sleeping now." << endl; mutexCout.unlock(); boost::this_thread::sleep(boost::posix_time::seconds(4)); mutexCout.lock(); cout << "MAIN: About to interrupt thread." << endl; mutexCout.unlock(); testThread.interrupt(); // Segmentation fault occurs around here during program execution. mutexCout.lock(); cout << "MAIN: Sent interrupt to thread." << endl; mutexCout.unlock(); testThread.join(); cout << "MAIN: Thread has ended." << endl; return 0; }

5 12