- Boost - lists.boost.org

boost_thread-vc80-mt-1_43.dll "the application failed to inialize properly"
by Clark Sims 14 Jan '11

14 Jan '11

I can link to boost_thread-vc80-mt-1_43.lib with no problem, but when I try to run the executable, I et an error The application failed to initialize properly )0xc0150002) Clico on OK to terminate the application. Does anyone know how to fix this?

1 0

TTI library in the sandbox
by Edward Diener 14 Jan '11

14 Jan '11

I have uploaded to the sandbox 'tti' directory version 1.0 of the TTI library. The TTI library, which is an abbreviation for the Type Traits Introspection library, allows a programmer to introspect at compile time the inner elements of a C++ type. The introspection process depends on specifying the name of the inner element by different macros for different types of elements, and then using a generated metafunction to determine whether that element exists within the enclosing type. The inner elements which can be introspected are type, class template, member data, member function, static member data, and static member function. The TTI library is based on the type_traits_ext portion of the Concept Traits Library, with improvements and additions, and also lifts functionality, for the purposes of orthogonality, from Boost.MPL regarding introspection of types and templates. The purpose of the library is to provide a consistent set of interfaces for doing compile-time introspection which other template metaprogrammers can use in their code. There is a readme.txt in the top-level sandbox tti directory, for anyone browsing the sandbox for interesting libraries, which replicates what is written here. There is a build.txt file in the doc subdirectory for building the documentation and running the tests. The documentation is also included as part of the sandbox files for those who can not build the docs. There is a list of todo items in the sandbox on which I will be working for the next release, but the library is already feature rich. The library has been tested and works with gcc 4.30, 4.4.0, 4.5.0-1 and VC++ 8.0, 9.0, and 10.0. It may also work with other compilers. There is a bug in versions of gcc prior to version 4 for which I will attempt to find a workaround if it is deemed important, which prevents it from working with the library. Questions, comments, suggestions, and bug reports are all welcome.

2 2

[ASIO] Compilation error on NetBSD
by Marek Dopiera 14 Jan '11

14 Jan '11

Hello everybody, this is my first post to this list. Recently I got an error when compiling a program which uses ASIO on NetBSD. It is related to kqueue. From what I see it is caused by passing descriptor_state* to EV_SET. Under NetBSD it should be intptr_t. Moreover, the udata field of kevent is implicitly cast to void* later on, which also causes an error. Explicit casts solve the issue. Maybe it's worth adding? Could someone with commit access check it and eventually correct it, please? I don't know how it is under FreeBSD, maybe an ifdef is needed to support both. The relevant compilation error (boost-1.44.0, NetBSD 5.1, i386, gcc 4.3.1) In member function 'void boost::asio::detail::kqueue_reactor::start_op(int, boost::asio::detail::socket_type, boost::asio::detail::kqueue_reactor::descriptor_state*&, boost::asio::detail::reactor_op*, bool)': asio/detail/impl/kqueue_reactor.ipp:132: error: invalid conversion from 'boost::asio::detail::kqueue_reactor::descriptor_state*' to '__intptr_t' asio/detail/impl/kqueue_reactor.ipp:136: error: invalid conversion from 'boost::asio::detail::kqueue_reactor::descriptor_state*' to '__intptr_t' asio/detail/impl/kqueue_reactor.ipp:142: error: invalid conversion from 'boost::asio::detail::kqueue_reactor::descriptor_state*' to '__intptr_t' asio/detail/impl/kqueue_reactor.ipp: In member function 'void boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&)': asio/detail/impl/kqueue_reactor.ipp:237: error: invalid conversion from '__intptr_t' to 'void*' [...] Regards

2 1

status of type traits addition (has_operator_xxx)
by Frédéric Bron 14 Jan '11

14 Jan '11

Here is the status of the type-traits addition: - I added the following operators: +=, *=, -=, /*, %=, &=, |=, ^=, <<, >>, >>=, <<=, prefix ++, prefix --, postfix ++, postfix -- so that the covered operators are now: - I added in the doc. the fact that private operators are not covered and lead to compile time errors - for operators on built-in types that require integer arguments (%, bitwise op.): I replaced a long list of specialiazation by an automatic detection Remaining work: 1. check what happens for pointer arguments, 2. implement trait for: . operator= . has_address_of_op<T> . has_dereference_op<T> . has_member_access_op<T> . has_subscript_op<T1 [,T2]> . has_pointer_to_member_op<T1 [,T2]> . has_comma_op<T1 [,T2]> . has_function_call_op<T,R [,P1, ...]> 3. have an MPL predicate for return value As I have only little time (full time work and 3 young children...), I will: - certainly do 1., - I will certainly leave 3. to somebody else in the future because I am not enough agile with MPL, - as for 2., 3 possibilities: (i) I do it but it will probably postpone the addition for a long time, (ii) I just leave it and I know is is a shame not to provide all operator detection (nobody's perfect) or (iii) somebody else agrees to add them and have them reviewed at the same time. Frédéric

3 2

[build]problems
by Matthias Schabel 13 Jan '11

13 Jan '11

Clean default install on OSX system with OpenMPI installed claims MPI is building, but does not build MPI component by default - it's a little confusing... ./bjam Building the Boost C++ Libraries. ...found 14 targets... ...updating 8 targets... common.mkdir bin.v2 common.mkdir bin.v2/libs common.mkdir bin.v2/libs/regex common.mkdir bin.v2/libs/regex/build common.mkdir bin.v2/libs/regex/build/darwin-4.2.1 common.mkdir bin.v2/libs/regex/build/darwin-4.2.1/debug darwin.compile.c++ bin.v2/libs/regex/build/darwin-4.2.1/debug/has_icu_test.o libs/regex/build/has_icu_test.cpp:12:30: error: unicode/uversion.h: No such file or directory libs/regex/build/has_icu_test.cpp:13:28: error: unicode/utypes.h: No such file or directory libs/regex/build/has_icu_test.cpp:14:27: error: unicode/uchar.h: No such file or directory libs/regex/build/has_icu_test.cpp:15:26: error: unicode/coll.h: No such file or directory libs/regex/build/has_icu_test.cpp: In function ‘int main()’: libs/regex/build/has_icu_test.cpp:23: error: ‘UErrorCode’ was not declared in this scope libs/regex/build/has_icu_test.cpp:23: error: expected `;' before ‘err’ libs/regex/build/has_icu_test.cpp:24: error: ‘UChar32’ was not declared in this scope libs/regex/build/has_icu_test.cpp:24: error: expected `;' before ‘c’ libs/regex/build/has_icu_test.cpp:25: error: ‘err’ was not declared in this scope "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -pedantic -g -dynamic -no-cpp-precomp -gdwarf-2 -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_HAS_ICU=1 -I"." -c -o "bin.v2/libs/regex/build/darwin-4.2.1/debug/has_icu_test.o" "libs/regex/build/has_icu_test.cpp" ...failed darwin.compile.c++ bin.v2/libs/regex/build/darwin-4.2.1/debug/has_icu_test.o... ...skipped <pbin.v2/libs/regex/build/darwin-4.2.1/debug>has_icu for lack of <pbin.v2/libs/regex/build/darwin-4.2.1/debug>has_icu_test.o... ...failed updating 1 target... ...skipped 1 target... ...updated 6 targets... Performing configuration checks - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam ...found 7 targets... ...updating 5 targets... common.mkdir bin.v2/libs/math common.mkdir bin.v2/libs/math/config common.mkdir bin.v2/libs/math/config/darwin-4.2.1 common.mkdir bin.v2/libs/math/config/darwin-4.2.1/debug darwin.compile.c++ bin.v2/libs/math/config/darwin-4.2.1/debug/has_gcc_visibility.o ...updated 5 targets... - ../config//has_gcc_visibility builds : yes ...found 47 targets... ...updating 1 target... darwin.compile.c++ bin.v2/libs/math/config/darwin-4.2.1/debug/has_long_double_support.o ...updated 1 target... - ../config//has_long_double_support builds : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Component configuration: - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - wave : building

2 1

[1.46.0] Unmerged changes to boost/detail
by Beman Dawes 13 Jan '11

13 Jan '11

The following files in boost/detail have not been merged to trunk. If appropriate, these should be merged. container_fwd.hpp wash 28 Dec 2010 endian.hpp johnmadddock 26 May 2010 extended_integer.hpp dwalker 24 Jul 2008 iomanip.hpp wash 08 Dec 2010 Thanks, --Beman PS: Who is "wash"?

6 13

Compile boost python extension using IDE on windows
by Raul Durand 13 Jan '11

13 Jan '11

Hi guys, I have a extension on Linux that uses boost python with no problems. Now I want to compile my extension on Windows, so I downloaded the precompiled boost libraries from: http://www.boostpro.com/download/boost_1_44_setup.exe I tried to compile my extension on windows using Visual Studio c++ 2008 express edition. I followed all the instructions from: http://boost.cppll.jp/HEAD/libs/python/doc/building.html to use an IDE to compile my own project and obtain a dll. I included all sources and libs and turned on RTTI and changed the debug and release builds to Multi-thread dll debug and Multi-thread dll release. All compilation process is successful. The problem is during linking appears *some warnings as*: 1> Creating library C:\My Dropbox\codes\fem\pyfem\Debug\pyfem.lib and object C:\My Dropbox\codes\fem\pyfem\Debug\pyfem.exp 1>libfembase.obj : warning LNK4217: locally defined symbol ??0str_base@detail@python@boost@@IAE@PBD@Z (protected: __thiscall boost::python::detail::str_base::str_base(char const *)) imported in function "public: __thiscall boost::python::str::str(char const *)" (??0str@python@boost@@QAE@PBD@Z) 1>libfembase.obj : warning LNK4217: locally defined symbol ?? 1str_base@detail@python@boost@@QAE@XZ (public: __thiscall boost::python::detail::str_base::~str_base(void)) imported in function "public: __thiscall boost::python::str::~str(void)" (??1str@python@boost@ @QAE@XZ) 1>libfembase.obj : warning LNK4217: locally defined symbol ?throw_error_already_set@python@boost@@YAXXZ (void __cdecl boost::python::throw_error_already_set(void)) imported in function "int __cdecl boost::python::len(class boost::python::api::object const &)" (?len@python@boost@@YAHABVobject@api@12@@Z) *and some errors as:* 1>boost_python-vc90-mt-gd-1_44.lib(dict.obj) : error LNK2019: unresolved external symbol __imp__PyDict_Items referenced in function "public: class boost::python::list __thiscall boost::python::detail::dict_base::items(void)const " (?items@dict_base @detail@python@boost@@QBE?AVlist@34@XZ) 1>boost_python-vc90-mt-gd-1_44.lib(dict.obj) : error LNK2019: unresolved external symbol __imp__PyDict_Keys referenced in function "public: class boost::python::list __thiscall boost::python::detail::dict_base::keys(void)const " (?keys@dict_base @detail@python@boost@@QBE?AVlist@34@XZ) 1>boost_python-vc90-mt-gd-1_44.lib(dict.obj) : error LNK2019: unresolved external symbol __imp__PyDict_Update referenced in function "public: void __thiscall boost::python::detail::dict_base::update(class boost::python::api::object const &)" (?update@dict_base@detail@python@boost@ @QAEXABVobject@api@34@@Z) 1>boost_python-vc90-mt-gd-1_44.lib(dict.obj) : error LNK2019: unresolved external symbol __imp__PyDict_Values referenced in function "public: class boost::python::list __thiscall boost::python::detail::dict_base::values(void)const " (?values@dict_base @detail@python@boost@@QBE?AVlist@34@XZ) 1>C:\My Dropbox\codes\fem\pyfem\Debug\pyfem.dll : fatal error LNK1120: 133 unresolved externals 1>Build log was saved at "file://c:\My Dropbox\codes\fem\pyfem\Debug\BuildLog.htm" 1>pyfem - 230 error(s), 56 warning(s) *#############* I got the same warnings and errors using bjam. I have been successful compiling and linking as a static library pyfem.lib using VS, but it does not work as a python extension even renaming to .pyd. - What I am missing to obtain the dll for my extension using VS? - Is it possible to create a boost python extension using VS C++ 2008 express edition? - I am using Win7 64 bits and Python 2.6 64 bits, so using boost 64 bit binaries is mandatory? Thanks. Raul Durand

2 1

[server] Continuing problems with svn operations
by Beman Dawes 13 Jan '11

13 Jan '11

I'm using svn a lot as part of the run-up to 1.46.0, but am having trouble. svn operations are very slow, and often fail. A typical error message is: Error: REPORT of '/svn/boost/!svn/vcc/default': Could not read chunk size: An existing Error: connection was forcibly closed by the remote host. Error: (https://svn.boost.org) Can anything be done about svn problems? I know Rene has already done a lot of work trying to improve the situation, but there are still serious performance problems. --Beman

3 2

[1.46.0][Date_Time] Could someone please commit some of the simple uncontroversial patches?
by KTC 13 Jan '11

13 Jan '11

Hi, Release time code freeze is coming again, please could anyone have a quick glance at <https://svn.boost.org/trac/boost/query?status=assigned&status=new&status=re…> and commit some of the simple uncontroversial patches? Some of them have been around for quite a while..... Pretty please? :) KTC

2 1

Development Practices (Proposal Progress)
by Dean Michael Berris 13 Jan '11

13 Jan '11

Hi Everyone, I was looking around at the Trac wiki and saw that there's a page called "ImprovingPractices". It's https://svn.boost.org/trac/boost/wiki/ImprovingPractices if you want to look. The Objectives stated on the page are definitely the same ones I am looking to address with a proposal I was thinking of writing from scratch. A quick read through definitely seems to me that there is significant overlap between what I had in mind and what's already in this document. One thing that doesn't seem to be in this document, is how to get new libraries into a Boost distribution. I'm not sure if this part should be in the same document either, but I really do think that somehow the continuity between the development of a library for inclusion into Boost and the release procedure should be in-tune. The document also assumes that the development of a library happens in the same repository -- mainly because it assumes that subversion is going to be used exclusively. That's understandable, but in the case of a proposal to support Git-based libraries as well I wonder whether it's alright if I edit this document for the proposed enhancements. So my question would be: - What would be the best way for me to solicit feedback on a proposal that tweaks the current process? Is editing this wiki page the way or should I create a new one? - Because there a number of parts of the proposal I'm going to write that deal with things on the front-end of the process (the interest-gathering, development (collaborative or otherwise), and review/inclusion part) as well as the back-end of the process (distribution maintenance, bug fixing / patching, and release management / packaging) is it better if these areas are described in different Wiki pages or should one page with different sections suffice? - Is the Wiki the best place to put this? Would others be more comfortable in a different means of looking at and commenting on a complete proposal? Thanks in advance and I definitely look forward to feedback and guidance. -- Dean Michael Berris about.me/deanberris

3 3