January 2013 - Boost-users - lists.preview.boost.org

How to build boost out-of-tree?
by Keitel, Tino (ALC NetworX GmbH) 31 Jan '13

31 Jan '13

Hi, I want to build boost out-of-tree. Usually, this is done like this: $ mkdir /path/to/build $ cd /path/to/build $ /path/to/source/configure $ make The actual source is not modified, all output is written in the build directory. The best I could find was http://www.boost.org/doc/libs/1_52_0/more/getting_started/unix-variants.htm…, but the bootstrap.sh step will still modify the source directory. How can I do a real out-of-tree build of boost? Regards, Tino

1 0

boost linkage problem
by Dave Dyer 30 Jan '13

30 Jan '13

I'm trying to construct a small library of wrappers for boost-using functions. In my test environment that links with this library (a windows executable) everything is fine. The working environment doesn't name any libraries explicitly. In another environment (the one I'm actually interested in) I get a large number of linkage errors, apparently seeking libstdc++ A small sample: 1>sharedmem-debug-x64.lib(sharedmemory.obj) : warning LNK4217: locally defined symbol ??1?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAA@XZ (public: __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::~basic_string<char,struct std::char_traits<char>,class std::allocator<char> >(void)) imported in function "public: static bool __cdecl boost::interprocess::shared_memory_object::remove(char const *)" (?remove@shared_memory_object@interprocess@boost@@SA_NPEBD@Z) 1>sharedmem-debug-x64.lib(sharedmemory.obj) : warning LNK4217: locally defined symbol ?c_str@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEBAPEBDXZ (public: char const * __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::c_str(void)const ) imported in function "public: static bool __cdecl boost::interprocess::shared_memory_object::remove(charconst *)" (?remove@shared_memory_object@interprocess@boost@@SA_NPEBD@Z) The non-working link is a complex environment, but I'm stumped why it doesn't link, or how to get it to link.

1 0

[phoenix] segmentation fault with valarray
by Philipp Schwaha 30 Jan '13

30 Jan '13

Hi all! I have worked with phoenix together with valarray and am currently stumbling over a case of segmentation fault. I construct the following phoenix expression boost::phoenix::at_c<0>(arg1) += boost::phoenix::at_c<1>(arg1) / val(mass) * arg2 I then feed a std::tuple<std::valarray<double>, std::valarray<double>> to it. It compiles nicely with gcc (4.6 & 4.7) using boost 1.52 as well as trunk. The resulting executable then proceeds to segfault, however. I have put together a small example (c++11) demonstrating my problem. The valarray's memory should already be reserved from original initialization. Performing the same operations manually with just the valarray not in phoenix seems to work fine. Am I missing something or doing something stupid here? thanks for any help! cheers Philipp

3 4

[threadpool] from your experience, is it safe to use threadpool with recent boost release?
by Frédéric Bron 30 Jan '13

30 Jan '13

Dear community, I found the threadpool library very useful (http://threadpool.sourceforge.net/) Apparently, it was designed for boost 1.37.0 and seemed to target inclusion in boost but probably did never go to a review because its author had not enough time to meet all requirements for boost inclusion, in particular, documentation. However, it is ready to be used with boost as is can just be untared in the boost include directory. I have tried to use it with boost 1.51.0 and it seems to work nicely. Before using it for long term projects, I was wondering if some of you use this library with success together with a rather recent boost release? Do you experience any issue or everything is just fine. Any chance that the latest changes in the thread library (http://thread.gmane.org/gmane.comp.lib.boost.devel/237484) would impact threadpool? Regards, Frédéric

4 6

hey
by Hossein Haeri 30 Jan '13

30 Jan '13

hey have a look http://www.com-im5.net/finance/ Hossein

1 0

[boost 1.47] boost::interprocess::scoped_lock<boost::interprocess::named_recursive_mutex> and fork() (linux)
by Frank Bergemann 30 Jan '13

30 Jan '13

Hello, i have a problem with boost::interprocess::scoped_lock<boost::interprocess::named_recursive_mutex> and using that one recursively in a unix (linux) fork() process environment. I.e. I create the boost::interprocess::named_recursive_mutex in a root process, then fork a number of child processes and those synchronize each other via boost::interprocess::scoped_lock<boost::interprocess::named_recursive_mutex>. When i use the named_recursive_mutex in a recursive way, the 2nd instance of the scoped_lock<> of it hangs (for one of the children, the first one, which tries to do a recursive lock.) I didn't have an issue without recursions (before i just used named_mutex - but i need to protect an application level region on a higher level now). And i didn't have a problem with a test program that does NOT fork(), which i start #10 instances on linux in parallel, and which also uses nested scoped_lock<>'s for each of them. Does anybody know about issue of boost::interprocess::named_recursive_mutex or boost::interprocess::scoped_lock<boost::interprocess::named_recursive_mutex> for unix/linux fork()? Do i have to create my named_recursive_mutex AFTER the fork() for each process instance? (i use m_mutex = boost::interprocess::named_recursive_mutex(boost::interprocess::open_or_create, _shmId.c_str())). I read about this here: http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-usi… It talks about need to call |pthread_mutex_init()|. Other pages seems to indicate, that there is only a problem, when i lock a mutex and then fork(), inheriting the lock to parent and child process. - many thanks! best regards, Frank

1 0

how to create smart pointer array?
by young 30 Jan '13

30 Jan '13

What is wrong with: boost::scoped_ptr<byte> buff[10]; for(int i=0; i<10; i++) { int size = 2*i + 100; buff[i] = boost::scoped_ptr<byte>(new byte[size]); } ... -- View this message in context: http://boost.2283326.n4.nabble.com/how-to-create-smart-pointer-array-tp4642… Sent from the Boost - Users mailing list archive at Nabble.com.

3 2

Simulating for loop iteration with iota
by Algocoders . 30 Jan '13

30 Jan '13

We have written a free chapter on "Simulating for loop iteration with iota" @ http://www.algocoders.com/sites/default/files/chapter1_c%2B%2B11algorithms_… HTH, Cheers, Algocoders http://www.algocoders.com/

1 0

Building boost on Windows
by John Lilley 30 Jan '13

30 Jan '13

I am trying to figure out which libraries to build on Windows. I really only need "polygon" and "geometry". But what libraries these dependent on that also need to be built? I've tried to query which will be built and I'm not getting the expected results, for example: $ ./b2 --show-libraries --build-type=complete The following libraries require building: - chrono - context - date_time - exception - filesystem - graph - graph_parallel - iostreams - locale - math - mpi - program_options - python - random - regex - serialization - signals - system - test - thread - timer - wave Hmmmm... where is polygon and geometry? $ ./b2 --show-libraries --build-type=complete --with-geometry error: wrong library name 'geometry' in the --with-<library> option. Help please?

2 3

Custom library names
by John Lilley 30 Jan '13

30 Jan '13

How does one build boost with custom library/DLL names? There are two reason for this -- Our software simultaneously runs 32-bit and 64-bit versions of itself, and things are easier if the library names reflect this (e.g. inject _x64_ and _x86_ into the names). -- If we have customized Boost in any way, we want to give it a unique name so that it cannot possibly be incorrectly loaded by other code. Thanks, John Lilley

2 2