- Boost - lists.boost.org

[boost 1.35][thread] Compile error with GCC 3.2
by Alexander Dong Back Kim 01 Sep '08

01 Sep '08

Dear members, I wrote an application using boost thread. It compiled well with GCC 3.4 but not with 3.2. I'm using Boost version 1.35. When I compile the application it shows the following error messages... /usr/local/include/boost-1_35/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pt hreads (Solaris) or -mthreads (Mingw32)" /usr/local/include/boost-1_35/boost/thread/detail/platform.hpp:67:9: #error "Sorry, no boost threads are available for this platform." /usr/local/include/boost-1_35/boost/thread/thread.hpp:19:2: #error "Boost threads unavailable on this platform" /usr/local/include/boost-1_35/boost/thread/condition_variable.hpp:18:2: #error "Boost threads unavailable on this platform" /usr/local/include/boost-1_35/boost/thread/condition.hpp:13: syntax error before `;' token /usr/local/include/boost-1_35/boost/thread/mutex.hpp:18:2: #error "Boost threads unavailable on this platform" /usr/local/include/boost-1_35/boost/thread/once.hpp:18:2: #error "Boost threads unavailable on this platform" /usr/local/include/boost-1_35/boost/thread/once.hpp:23: type specifier omitted for parameter `once_flag' /usr/local/include/boost-1_35/boost/thread/once.hpp:23: syntax error before `&' token /usr/local/include/boost-1_35/boost/thread/once.hpp: In function `void boost::call_once(...)': The codes were compiled well with boost 1.32 but once I upgraded to 1.35, this error starts occurring. Any ideas or suggestions are welcomed and appreciated. best regards, Alex Kim

2 2

[boost 1.35] Linking problem with GCC 3.2
by Alexander Dong Back Kim 01 Sep '08

01 Sep '08

Hi members, I'm using both GCC 3.2 and 3.4 in different linux machines. The application uses a number of BOOST libraries such as program_options, iosterams, thread and system. When I compiled the application with GCC 3.4 (of course linking correct library files like "libboost_program_options-gcc34-mt"), it compiled well and works well. I did "ldd" to see what library files are linked... and it says... libpthread.so.0 => /lib/tls/libpthread.so.0 (0x0048a000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x005e8000) libm.so.6 => /lib/tls/libm.so.6 (0x00372000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00555000) libc.so.6 => /lib/tls/libc.so.6 (0x0023e000) /lib/ld-linux.so.2 (0x00224000) Now, I compiled the same application and link different gcc version of boost library files because it uses GCC 3.2 instead. I compiled it and there was no compile-time error but it cannot be executed because it can't find the target library files. I did "ldd" for the application and now it has all the boost library files... libpthread.so.0 => /lib/tls/libpthread.so.0 (0x0038d000) libboost_system-gcc32-mt-1_35.so.1.35.0 => not found libboost_thread-gcc32-mt-1_35.so.1.35.0 => not found libboost_serialization-gcc32-mt-1_35.so.1.35.0 => not found libboost_program_options-gcc32-mt-1_35.so.1.35.0 => not found libboost_iostreams-gcc32-mt-1_35.so.1.35.0 => not found libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x00b8e000) libm.so.6 => /lib/tls/libm.so.6 (0x007a6000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00179000) libc.so.6 => /lib/tls/libc.so.6 (0x00182000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00d66000) Both machine has the same boost 1.35. Only differences is they have different versions of GCC (3.2 and 3.4). Is there any idea or hints where this problem comes from??? regards, Alex Kim

3 4

F# Units of Measurement
by Mårten Rånge 01 Sep '08

01 Sep '08

This is not C++ but since it was used as an example in the boost mpl book maybe it could insterest some. http://blogs.msdn.com/andrewkennedy/ -- Mårten

2 1

lifetime of ranges vs. iterators
by Arno Schödl 01 Sep '08

01 Sep '08

> When stacking N difference_ranges, the size difference between "fat" and "lean" > iterators is 2^N. Thus in fully generic code where you don't know anything about > the stacking depth, even generating a single fat iterator carries a potentially > exponential penalty. > This fact makes me think that range is not merely a fancy name for a pair of > iterators but a concept in its own right between containers and iterators. > Generic algorithms must be written on the basis of ranges rather than iterators > or take a significant performance hit. To be fair, this hit could be avoided by storing the sub-iterators of the difference_iterator in their factored form, e.g., m_ittrav/m_ittravEnd would be stored as m_ittrav/m_ittravEnd/m_travcommon. But this would put a big burden on the compiler to optimize the frequent compose/decompose operations. For example: *m_ittrav; would become *compose( m_ittrav, m_travcommon ) // common data not used at all and ++m_ittrav; would become m_ittrav=decompose( ++compose( m_ittrav, m_travcommon ) ).first; -Arno -- Dr. Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

1 0

Boost 1.36.0 release notes missing Circular Buffer changes
by Dean Michael Berris 01 Sep '08

01 Sep '08

Hi, I took a look at the code in trunk and in 1.36.0, and I notice the release notes don't mention the change in behavior of Boost.Circular_Buffer WRT the default constructor. Should we add: Circular Buffer: * default constructor now doesn't allocate memory, and sets the capacity of the buffer to 0 To the 1.36 release notes? -- Dean Michael C. Berris Software Engineer, Friendster, Inc.

1 0

Re: [boost] [review wizard/admin] Not-yet-committed, but accepted libraries
by JOAQUIN M. LOPEZ MUÑOZ 31 Aug '08

31 Aug '08

________________________________________ De: boost-bounces(a)lists.boost.org [boost-bounces(a)lists.boost.org] En nombre de Ronald Garcia [garcia(a)cs.indiana.edu] Enviado el: sábado, 30 de agosto de 2008 18:56 Para: Boost mailing list CC: John R. Phillips Asunto: [boost] [review wizard/admin] Not-yet-committed, but accepted libraries > > A few libraries have been reviewed and accepted into boost, but have > not yet appeared in SVN as far as I can tell. Could some light be > shed on the status of the following libraries? Apologies if I have > simply overlooked any of them: > > Flyweight (Joaquín Mª López Muñoz) I'm glad you ask :) The review raised some important issues that only during this summer I've had the time to attack. I've got everything ready for a post-review version during the following week. My target release is Boost 1.38. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[pointer container] Wishlist: Iterating through nullable vectors and compiler firewalls
by Andrew Hain 31 Aug '08

31 Aug '08

Two quick queries. Would it make sense to have the iterator increment and decrement operators and begin() member function of ptr_vector< nullable<> > skip missing records so that applications have no need to check? What is stopping pointer container classes from being used with opaque types as a compilation firewall? -- Andrew Hain Oasys http://www.oasys-software.com

2 2

[log] Yet more questions for Andrey: formatting severity
by Igor Nazarenko 31 Aug '08

31 Aug '08

By default, severity is printed as integer. What's the easiest way to print the corresponding string (e.g. "info" for severity 0, "warn" for severity 1, and so on)? I tried defining operator<< for my severity enum, but attr<severity_level> doesn't work; that is, the output operator doesn't get invoked (I assume because attribute "Severity" is internally of type "int" and not of my enum type). Thanks a lot! Igor

3 4

Re: [boost] [Boost-users] [filesystem][xpressive] Hotfix patches available for 1.36.0
by Mat Marcus 31 Aug '08

31 Aug '08

On Fri, Aug 29, 2008 at 1:36 PM, Eric Niebler <eric(a)boostpro.com> wrote: > Michael Marcin wrote: >> >> If the fixes are not critical enough to justify making a point release >> than they should wait until the next release. > > So you're against hotfixes. <shrug> I would say, take the hotfix if you are > experiencing the problem addressed by the hotfix. Otherwise, wait for the > next release. > > -- > Eric Niebler > BoostPro Computing > http://www.boostpro.com For some of us the answer is not <shrug>. Are hotfixes really the way forward? Not to pick on filesystem, threads or xpressive, but hotfixes are a bit difficult to manage in a coporate environment. It's hard enough to get boost accepted/updated without having to defend against people who argue that it's too risky to use boost due to "inadequate quality control" e.g. "boost 1.35.0 didn't work out of the box (windows thread bugs, filesystem compilation errors, etc.), boost 1.36.0 doesn't work out of the box, and there are no dot-releases planned". It really helps if there is a perception of stable, high quality, official, numbered releases. - Mat

5 8

[review wizard/admin] Not-yet-committed, but accepted libraries
by Ronald Garcia 31 Aug '08

31 Aug '08

A few libraries have been reviewed and accepted into boost, but have not yet appeared in SVN as far as I can tell. Could some light be shed on the status of the following libraries? Apologies if I have simply overlooked any of them: Flyweight (Joaquín Mª López Muñoz) Binary Int (Matt Calabrese) Floating Point Utilities (Johan Råde) Factory (Tobias Schwinger) Forward (Tobias Schwinger) Scope Exit (Alexander Nasonov) Time Series (Eric Niebler) Property Tree (Marcin Kalicinski) -- No documentation in SVN Any information on the whereabouts of these libraries would be greatly appreciated. Cheers, ron

2 1