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

arm-elf-gcc 4.0.1 class alignment
by Pierre-Andre van Leeuwen 28 May '12

28 May '12

Hi Not sure if this belongs on this list or the Boost.Build list, but the problem exists when using Boost as well as building it. I'm using Boost with the ARM-ELF-GCC toolchain with gcc version 4.0.1. When building the Boost serialization library, I get the following error: ./boost/archive/basic_binary_oarchive.hpp:80: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE<false>' It turns out that sizeof(class_id_type ) == 4 in stead of 2, where class_id_type is defined as follows: class class_id_type { private: typedef int_least16_t base_type; base_type t; ... }; Using a toolchain with a more recent gcc version (arm-none-eabi-gcc 4.4.1) works correctly, but unfortunately I need to get Boost working with the old toolchain as well. I have tried to add __attribute__ ((packed)) to the class declaration, but that breaks as well (cannot bind packed field in operator int_least16_t). Is there anything I can do to rectify the situation? My user-config.jam contains the following: using gcc : armelf : "arm-elf-gcc.exe" : <cflags>-nostdlib <cxxflags>-DBOOST_NO_INTRINSIC_WCHAR_T <cxxflags>-D__OAT_API_VERSION__=637 <cxxflags>-D__WIP_PLUGIN_VERSION__=543 <cxxflags>-D__arm <cxxflags>-D_LITTLE_ENDIAN <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.os.model.6.37.0.201202060950_6.37.0.201202060950\resources/ADL/itf <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.os.model.6.37.0.201202060950_6.37.0.201202060950\resources/ADL/basic <cxxflags>-IC:\Program Files (x86)\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.plugin.model.WIP.5.43.0.201202100610_5.43.0.201202100610\resources/WIP/itf <cxxflags>-fshort-enums <cxxflags>-fdollars-in-identifiers <cxxflags>-nostartfiles <cxxflags>-fno-strict-aliasing <cxxflags>-fno-common <cxxflags>-fomit-frame-pointer <cxxflags>-mthumb-interwork <cxxflags>-mthumb <cxxflags>-march=armv5te <cxxflags>-msoft-float <cxxflags>-mfpu=fpa <cxxflags>-mapcs <cxxflags>-mno-apcs-stack-check <cxxflags>-mlittle-endian <architecture>arm <address-model>32 ; I'm building boost with the following command .\b2 variant=debug,release link=static threading=single toolset=gcc-armelf --debug-configuration --debug-building --with-serialization stage Any help will be appreciated. Pierre-Andre van Leeuwen Director | Gendac (Pty) Ltd<http://www.gendac.com/>

1 0

mpl and fusion containers: numbered vs variadic
by MM 27 May '12

27 May '12

Hello, Is it true that as a general rule, using the numbered version instead of the variadic version yields faster compile times? Or is it just about compilers supporting variadic templates? MM

3 3

BOOST_RESULT_OF_USE_DECLTYPE and Boost.Optional ?
by John M. Dlugosz 27 May '12

27 May '12

I turned on BOOST_RESULT_OF_USE_DECLTYPE and used boost::result_of because the std::tr1::result_of that comes with VS10 doesn't use declspec at all and thus doesn't work right with lambda functions. This passes my unit tests, but fails on a piece of code that has a function returning an instantiation of boost::optional. It seems confused as to whether the value held in the optional is as-specified or has a reference added to it. I wonder if this is a specific issue with optional that might be addressed/worked-around/patched, or perhaps there is a way to enable declspec-based testing just for the code that wanted it and not globally? —John

2 1

Why does the fusion::set repeated keys?
by niXman 27 May '12

27 May '12

Hi, In this simple code, I expect that the size of the fusion::set is equal to one, because keys are the same. Why the size is equal to two? #include <boost/fusion/container/set.hpp> #include <boost/fusion/include/set.hpp> #include <boost/fusion/container/set/set_fwd.hpp> #include <boost/fusion/include/set_fwd.hpp> #include <boost/fusion/sequence/intrinsic/size.hpp> #include <boost/fusion/include/size.hpp> #include <iostream> int main() { typedef boost::fusion::set<int, int> set1; set1 s1; std::cout << "size1 = " << boost::fusion::result_of::size<set1>::type::value << ", size2 = " << boost::fusion::size(s1) << std::endl; } http://liveworkspace.org/code/166b54cdd208f7b252bf1f38a1a6ec4b Thanks! -- Regards, niXman ___________________________________________________ Dual-target(i686/x86_64) MinGW compiler for i686/x86_64 hosts: http://sourceforge.net/projects/mingwbuilds/

2 1

[asio] Boost asio mailing list
by Edward Diener 27 May '12

27 May '12

How do I subscribe to the asio mailing list ?

2 1

BOOST_RESULT_OF_USE_DECLTYPE and Boost.Optional ?
by John M. Dlugosz 27 May '12

27 May '12

Hmm, the error isn't quite what I said: 1>V:\Trunk\stable\src\Include\Tools/async.h(268): error C2664: 'boost::unique_future<R>::unique_future(boost::unique_future<R> &)' : cannot convert parameter 1 from 'boost::unique_future<R>' to 'boost::unique_future<R> &' 1> with 1> [ 1> R=boost::optional<in_addr> & 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> 1> ] 1> and 1> [ 1> R=boost::optional<in_addr> & 1> ] But my other test cases of using unique_future (with simple types) work OK. —John

1 0

udp client
by Christer Borgqvist 27 May '12

27 May '12

Hi, I use the HTTP server 3 example, i want to dump all the request and response to a thread queue and using a udp client to send to syslog, how should i do that. / Christer

1 1

logger progress?
by Victor Whiskey Yankee 26 May '12

26 May '12

Hello, How is the boost logger going for proper inclusion? Thanks, Vic

2 1

Apple "Block" closures and boost::function
by John M. Dlugosz 26 May '12

26 May '12

I'm looking at using Apple's proprietary closure blocks as a substitute for C++ lambda functions on a project that needs to be portable between Mac (LLVM 3.1, but not using the C++0x dialect compiler switch) and Windows (Visual Studio 10). The project uses Boost.TR1 to supply std::tr1::function and related stuff on the Mac build. Now I found that the compiler handles the nonstandard block objects in Functor-like template situations in a manner perfectly analogous to C-style pointers to functions. I can even assign one to a boost::function with no complaint! The only issue seems to be that it never calls Block_copy/Block_release. So it works OK for passing them to STL algorithms that uses them on the spot, but will probably do bad things if used in general. Does anybody have something ready-made, to efficiently add the copy/destroy semantics to functors that hold such "blocks"? That would be much more efficient than wrapping them in another layer. Or, any pointers to the Boost innerds for doing that myself? Thanks, —John

1 0

[Test] main for BOOST_TEST_DYN_LINK with manual registration
by Rhys Ulerich 25 May '12

25 May '12

What from example 15 from the Boost.Test "Manually registered test suites" documentation[1] needs to change if instead of #include <boost/test/included/unit_test.hpp> one used #define BOOST_TEST_DYN_LINK #include <boost/test/unit_test.hpp> ? >From reading [1] and [2], one needs to provide a main() that invokes the unit_test_main, but I'm at a loss for what it would look like... I don't think I'm running afoul of BOOST_TEST_ALTERNATIVE_INIT_API from reading <boost/test/unit_test.hpp> where the main() definition cares nothing about that #define, but I could be wrong. Help or a known-good example much appreciated, Rhys [1] http://www.boost.org/doc/libs/1_49_0/libs/test/doc/html/utf/user-guide/test… [2] http://www.boost.org/doc/libs/1_49_0/libs/test/doc/html/utf/user-guide/test…

1 2