February 2011 - Boost-users - lists.preview.boost.org

using the sandbox(es)
by Alle Meije Wink 24 Feb '11

24 Feb '11

Dear all, My code uses some files from the boost sandbox repository as well as from boost. To be able tom compile my own code and stay up to date, I have downloaded and installed boost (svn, bjam) and downloaded the sandbox (svn). Now building boost was simple: create a build/ directory and call "bjam -a --toolset=gcc --build-dir=build --variant=release --link=shared --threading=multi --runtime-link=shared install" or something very similar In the sandbox things seem to be a bit differently. Using bjam in the same style as above does not work, in particular any "bjam ... install" comes back with a warning/notice notice: could not find main target install notice: assuming it is a name of file to create. don't know how to make <e>install ...found 1 target... ...can't find 1 target... and no files are installed (i.e. no files are copied to /usr/local/include). Is it possible to install the boost-sandbox files to /usr/local using bjam? Or is this not the way the sandbox should be used? many thanks Alle Meije Wink

3 7

BOOST_ASIO_DISABLE_FENCED_BLOCK
by tkolo＠poczta.fm 24 Feb '11

24 Feb '11

Hi, I had to set BOOST_ASIO_DISABLE_FENCED_BLOCK to be able to copmile on Solaris 9. What does this exacly disables because I can't find any documentation for it? Problems I have encountered are similar to those: https://svn.boost.org/trac/boost/ticket/4376. Regards, Tomek. ---------------------------------------------------------------- Jedz ile chcesz i chudnij! Sprawdź >>> http://linkint.pl/f2904

1 0

[boost][boost-users][ICL] ICL Compilation errors. Ticket #5207
by Joachim Faulhaber 24 Feb '11

24 Feb '11

Hi John, lists, I am replying to your ticket #5207 on the lists because I am afraid that you walked into a trap that others can fall into as well. In the ITL, the precursor of Boost.ICL there was a single polymorphic interval class template: itl::interval. Due to input from the list during the review I split up this "one size fit's all" template in smaller classes according to static and dynamic interval concepts. In order to help ITL users to have a simple transition from ITL to ICL I wrote a template icl::interval. icl::interval is a meta function that yields the right interval type dependent on the instance type e.g. : BOOST_STATIC_ASSERT(( boost::is_same< interval<int>::type , discrete_interval<int> >::value )); So ITL users could move from ITL to ICL just by appending a '::type' to all occurrences of 'interval<T>' So please note that interval<myType> myInterval; can not be used as an interval type in ICL functions. Please use interval<myType>::type myInterval; or one of the specific interval types discrete_interval, continuous_interval, (dynamic borders) closed_interval, right_open_interval, left_open_interval, open_interval (static borders) e.g. discrete_interval<int> myInterval; See examples http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/e… http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/e… http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/e… and docs http://www.joachim-faulhaber.de/boost_icl/doc/libs/icl/doc/html/boost_icl/i… for more detail. This reduces John's non compilable ICL statements in the following way: BOOST_AUTO_TEST_CASE(ticket_5207) { icl::interval< int >::type int_interval; icl::interval_set< int > int_set; icl::interval_map< int, int > int_map; icl::interval_map< int, int >::element_type int_element; icl::interval_map< int, int >::segment_type int_segment; // The next 4 lines compile icl::lower( int_interval ); icl::upper( int_interval ); icl::first( int_interval ); icl::last( int_interval ); // The next 4 lines are *not* supposed to compile // according to the docs: icl::add( int_set, int_set ); icl::add( int_map, int_map ); icl::subtract( int_set, int_set ); icl::subtract( int_map, int_map ); int_set += int_interval; // compiles // Here you are right, John: // The next 4 lines should compile according // to the docs, but don't icl::disjoint( int_map, int_element ); icl::disjoint( int_map, int_segment ); icl::intersects( int_map, int_segment ); icl::intersects( int_map, int_element ); // Those four are pretty special. I doubt anyone will // use them. But I will complete the library here. } Thanks for using my library and helping to improve it. Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

2 11

Undefined reference to boost_serialization even though it is specified with -lboost_serialization
by Cedric Laczny 24 Feb '11

24 Feb '11

Sorry, my bad. Hit "Send" before being finished... So let's start again... I apologize. Hi, I have a program that uses serialization-functionality for some of the self- defined classes. I specify "-lboost_serialization" with the g++ and it works fine on my local machine. However, when I want to compile it on a remote machine, it fails. The remote machine is lacking >=boost-1.42 which is needed. Therefore I built (no install) boost-1.45 remotely (under /local/cedric/boost_1_45_0) and at least the configure-script (generated using autotools) seems to detect all the necessary libraries and headers (provided I specify them in the environment variables), on my local machine aswell as on the remote machine. Now the problem is, that I don't find the reason why it fails to compile my program remotely... Any ideas? Here's the command used for linking: /bin/bash ../libtool --tag=CXX --mode=link g++ -Wno-deprecated -g -O2 - lboost_serialization -L/local/cedric/boost_1_45_0/stage/lib -o test test- main.o ../includes/Parser/libparser.a -lgsl -lgslcblas -lm and an excerpt of the error (taken from the end): ... MicroCosmParser.cpp: (.text._ZN5boost13serialization6detail17singleton_wrapperINS0_25extended_type_info_typeidI15MicroCosmParserEEED0Ev[boost::serialization::detail::singleton_wrapper<boost::serialization::extended_type_info_typeid<MicroCosmParser> >::~singleton_wrapper()]+0x17): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::type_unregister()' MicroCosmParser.cpp: (.text._ZN5boost13serialization6detail17singleton_wrapperINS0_25extended_type_info_typeidI15MicroCosmParserEEED0Ev[boost::serialization::detail::singleton_wrapper<boost::serialization::extended_type_info_typeid<MicroCosmParser> >::~singleton_wrapper()]+0x1f): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::~extended_type_info_typeid_0()' MicroCosmParser.cpp: (.text._ZN5boost13serialization6detail17singleton_wrapperINS0_25extended_type_info_typeidI15MicroCosmParserEEED0Ev[boost::serialization::detail::singleton_wrapper<boost::serialization::extended_type_info_typeid<MicroCosmParser> >::~singleton_wrapper()]+0x39): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::~extended_type_info_typeid_0()' ../includes/Parser/libparser.a(MicroCosmParser.o): (.rodata._ZTVN5boost13serialization6detail17singleton_wrapperINS0_25extended_type_info_typeidI15MicroCosmParserEEEE[vtable for boost::serialization::detail::singleton_wrapper<boost::serialization::extended_type_info_typeid<MicroCosmParser> >]+0x10): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::is_less_than(boost::serialization::extended_type_info const&) const' ../includes/Parser/libparser.a(MicroCosmParser.o): (.rodata._ZTVN5boost13serialization6detail17singleton_wrapperINS0_25extended_type_info_typeidI15MicroCosmParserEEEE[vtable for boost::serialization::detail::singleton_wrapper<boost::serialization::extended_type_info_typeid<MicroCosmParser> >]+0x18): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::is_equal(boost::serialization::extended_type_info const&) const' ../includes/Parser/libparser.a(MicroCosmParser.o): (.rodata._ZTIN5boost13serialization25extended_type_info_typeidI15MicroCosmParserEE[typeinfo for boost::serialization::extended_type_info_typeid<MicroCosmParser>]+0x18): undefined reference to `typeinfo for boost::serialization::detail::extended_type_info_typeid_0' ../includes/Parser/libparser.a(MicroCosmParser.o): (.rodata._ZTVN5boost13serialization25extended_type_info_typeidI15MicroCosmParserEE[vtable for boost::serialization::extended_type_info_typeid<MicroCosmParser>]+0x10): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::is_less_than(boost::serialization::extended_type_info const&) const' ../includes/Parser/libparser.a(MicroCosmParser.o): (.rodata._ZTVN5boost13serialization25extended_type_info_typeidI15MicroCosmParserEE[vtable for boost::serialization::extended_type_info_typeid<MicroCosmParser>]+0x18): undefined reference to `boost::serialization::detail::extended_type_info_typeid_0::is_equal(boost::serialization::extended_type_info const&) const' collect2: ld returned 1 exit status Best, Cedric

3 7

Help needed with successive calls to Asio routines using the plain old Windows API
by Adolfo Jimenez 24 Feb '11

24 Feb '11

Hi all: Using MS Visual Studio 2008 C++ for Windows 32 (XP brand), I try to construct a POP3 client managed from a modeless dialog box. As a first step, in the WM_INITDIALOG message in the dialog-box-procedure, I create a persistent object -say pop3- with all that Boost.asio stuff to do asynchronous connections. Some like: case WM_INITDIALOG: return (iniPop3Dlg (hDlg, lParam)); Here we assume that iniPop3Dlg() create the pop3 heap object -say pointed out by pop3p-, and then, connect with the remote server and initiate a session with the client’s id and password (USER and PASS commands). After that, the server is in TRANSACTION state. Then, in response to some user input, the dialog-box-procedure, call the appropriate function. Say: case IDS_TOTAL: // get how many emails in the server total (pop3p); return FALSE; case IDS_DETAIL: // get date, sender and subject for each email in the server detail (pop3p); return FALSE; Note that total() uses the POP3’s STAT command to get how many emails in the server, while detail() uses two commands consecutively; first STAT to get the total and then a loop with the GET command to retrieve the content of each message. As an aside: detail() and total() share the same subroutines -the STAT handle routine-, and when finished, both leaves the session as-is. That is, without closing the connection; the socket remains opened an the server in TRANSACTION state. When any option is selected by the first time, the things run as expected, obtaining the desired results. But when making the second chance, the connection hangs. A closer inspection show that the in the second chance, the first time that is use the statement socket_.get_io_service().run(); It never return. Note that all asynchronous wirte an read routines uses the same io_service, and the socket_.get_io_service().reset(); sentence prior to any io_service.run() Note also that all R/W operations also uses the same timer, who is reseted to cero wait afther each operation is completed: dTimer_.expires_from_now (boost::posix_time::seconds(0)); I suspect that the problem is in the io_service or in the timer, and the fact that subsequent executions occurs in a different load of the routine. As a first approach to mi problem, I hope that someone would bring some light in it, prior to a more detailed exposition of the -very few and simple- Asio routines involved.

1 0

Undefined reference to boost_serialization even though it is specified with -lboost_serialization
by Cedric Laczny 24 Feb '11

24 Feb '11

Hi, I have a program that used serialization-functionality for some of the self- defined classes. I specify "-lboost_serialization" with the g++ and it works fine on my local machine. However, when I want to compile it on a remote machine, that is unfortunately lacking Boost-1.42 (needed due to lookup_edge.hpp) it fails to compile

1 0

boost::interprocess::interprocess_semaphore::timed_wait - how to do a relative wait
by Jean-Sebastien Stoezel 24 Feb '11

24 Feb '11

Hi: I'm using boost::interprocess::interprocess_semaphore::timed_wait and boost::interprocess::message_queue::timed_received. I have to specify an absolute time to give up waiting/receiving. This works in most cases, except my application sometimes needs to adjust the PC clock. If the PC clock is adjusted backwards in time, then these function wait longer than they should (since the end time is fixed in the future). Ideally I would like to provide an absolute time instead, which would be independent of the time of day? The API doesn't seem to allow this. How can I do this? I guess I could also use a deadline timer (ASIO). Any help on this would be appreciated. Thanks, Jean

3 4

My Apologies -- Please Disregard
by Robert Pennington 23 Feb '11

23 Feb '11

All, If you received any emails from me today (from robpennington84(a)gmail.com), please disregard them; my account was targeted by a spammer. Those responsible have been sacked. Those responsible for sacking the people who have just been sacked, have also been sacked. Thanks, Rob Pennington

1 0

Re: [Boost-users] (no subject)
by Robert Pennington 23 Feb '11

23 Feb '11

Good result. 100% of pleasure... http://www.de-beste-casino-online.com/links.php?owgoogle=637

1 0

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

23 Feb '11

Hello Júlio, Thanks for your reply. I've tried to pass the libraries that I needed in a past attempt. It didn't help. If I don't specify any library to bootstrap.sh, all the libraries are built. This way, I'm sure I don't miss anything. It also makes the explanation of what I did more straightforward. I'll definitely have a closer look at the doc. I might have missed something, although it would be surprising to have to modify something in the configuration to make such a simple example build. Sincerely, Nicolas -----Original Message----- From: Júlio Hoffimann Sent: Wed 2/23/2011 3:54 AM To: boost-users(a)lists.boost.org Cc: Nicolas Chaumont Subject: Re: [Boost-users] [Filesystem] Symbol not found: boost::filesystem2::detail::status_api Hi Nicolas, It's my first time using Boost, but i think you missed the build steps. The Boost library is header-only, except this parts: http://www.boost.org/doc/libs/1_46_0/more/getting_started/unix-variants.htm… < http://www.boost.org/doc/libs/1_46_0/more/getting_started/unix-variants.htm… >For example, i'm using Boost.MPI and Boost.Random, my bootstrap.sh call is something like: ./bootstrap.sh --prefix=/your/desired/path --with-libraries=mpi,random I think you need to pass Filesystem to bootstrap.sh before anything. Also is a good idea read it's docs, because maybe you will need to edit some specific configuration files like i did in Boost.MPI. Regards, Júlio.

1 0