- Boost - lists.boost.org

Re: [boost] [1.45][Serialization] fails to cross-compile usingarm-linux-uclibc toolchain
by Alex Potapenko 24 Jan '11

24 Jan '11

Robert Ramey wrote: > BOOST_STATIC_ASSERT(sizeof(class_id_type) == sizeof(int_least16_t)); > BOOST_STATIC_ASSERT(sizeof(class_id_reference_type) == > sizeof(int_least16_t)); These should be investigated. before commenting out. It could be detecting something unexpected in a pre-requisite library. I'm afraid I haven't neither got the knowledge, nor the skills to investigate it myself :( In case you (or someone else) are willing to investigate it for me, here's a relatively simple way to trigger these errors: 1. Checkout the optware trunk: $ svn co http://svn.nslu2-linux.org/svnroot/optware/trunk optware 2. Build the toolchain: $ cd optware; make mbwe-bluering-target $ cd mbwe-bluering; make directories toolchain ipkg-utils 3. Replace make/boost.mk from the svn with the one attached to this letter 4. Cross-compile: $ make boost # while remaining in the mbwe-bluering directory Thanks in advance, Alex

1 0

Re: [boost] [Boost-bugs] [Boost C++ Libraries] #5111: BOOST_TR1_STD_HEADER bad on Solaris 11/stdcxx4
by Bryce Lelbach 23 Jan '11

23 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 23 Jan 2011 20:39:12 -0000 "Boost C++ Libraries" <noreply(a)lists.boost.org> wrote: > #5111: BOOST_TR1_STD_HEADER bad on Solaris 11/stdcxx4 > > this is likely because stdcxx4 resides in > /usr/include/stdcxx4/ > /usr/include/stdcxx4/ansi > there, which the config_all.hpp does not take into account and sets > BOOST_TR1_STD_HEADER inappropriately This was fixed for Pathscale - John, could you please modify the fix I made for Pathscale to apply to any toolchain using the apache/rw stdlib? - -- Bryce Lelbach aka wash boost-spirit.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAk08lxcACgkQ9cB/V3/s9EzcHwCdGCinVPCvyKbGDPs7LHa1DoIQ c3wAn1OO39wYkj1F5BmCSmjR7zW0oaGD =WQvl -----END PGP SIGNATURE-----

2 1

[process] How to run test cases
by Boris 23 Jan '11

23 Jan '11

As Boost.Process 0.3 has been released it would be great if the test cases are run on various platforms. So far I've tested Boost.Process on WinXP with MSVC 9.0, Cygwin with g++ 3.4.4 and Solaris with g++ 3.4.6 and Sun C++ 5.9. To make it as easy as possible for others to run the test cases here's a short description of how to proceed. Nearly all test cases depend on a program called "helpers". This program is built first and is started by many test cases as a child process. In order to find the program "helpers" the test cases must know its location. As there is no way to get the location at runtime it is hardcoded in the file libs/process/test/misc.hpp. As the location differs depending on what compiler is used YOU MUST CHECK FIRST THE PATH IN libs/process/test/misc.hpp! Otherwise most of the test cases will fail as they look for a program "helpers" in the wrong directory. As of today only those paths are correct and have been tested which are set for Windows, Cygwin and Solaris. Only after you have checked and maybe updated the path in libs/process/test/misc.hpp you should try to build and run the test cases: WinXP/MSVC 9.0 ************** With MSVC 9.0 you only need to open the Visual Studio 2008 Command Prompt, change to the directory with the test cases and run bjam: C:\boost_1_36_0\libs\process\test> ..\..\..\bjam.exe -q Cygwin/GCC 3.4.4 **************** On Cygwin it's important to know if the Boost libraries have been built for the POSIX or Windows API. By default Boost libraries on Cygwin use the Windows API. With the Windows API the Boost.Process test cases are not passed successfully though (there are compiler errors where I'm not sure currently if they are a Boost.Process problem and how they could be fixed). If you want to run the test cases on Cygwin you must (re-)build the Boost libraries to use the POSIX API: $ cd ~/boost_1_36_0 $ ./bjam cxxflags=-DBOOST_POSIX_API Afterwards you can run the test cases: $ cd ~/boost_1_36_0/libs/process/test $ ../../../bjam cxxflags=-DBOOST_POSIX_API -q Solaris/GCC 3.4.6 ***************** At first you have to put the following line in ~/user-config.jam: using gcc : : : <linker-type>sun ; Then start building the Boost libraries: $ cd ~/boost_1_36_0 $ ./bjam --toolset=gcc cxxflags=-mcpu=ultrasparc For the test cases to be passed successfully you must update Boost.Test. Change line 624 in ~/boost_1_36_0/boost/test/impl/execution_monitor.ipp temporarily to: - , m_CHLD_action( SIGCHLD, catch_system_errors, attach_dbg, alt_stack ) + , m_CHLD_action( SIGCHLD, false, attach_dbg, alt_stack ) It is important that the second parameter is false as the signal SIGCHLD should not be handled by the execution monitor and should not be reported as an error. Afterwards the test cases can be run: $ cd ~/boost_1_36_0/libs/process/test $ ../../../bjam --toolset=gcc cxxflags=-mcpu=ultrasparc -q Solaris/Sun C++ 5.9 ******************* Build the Boost libraries with the sun toolset: $ cd ~/boost_1_36_0 $ ./bjam --toolset=sun stdlib=sun-stlport For the test cases to be passed successfully you must update Boost.Test. Change line 624 in ~/boost_1_36_0/boost/test/impl/execution_monitor.ipp temporarily to: - , m_CHLD_action( SIGCHLD, catch_system_errors, attach_dbg, alt_stack ) + , m_CHLD_action( SIGCHLD, false, attach_dbg, alt_stack ) It is important that the second parameter is false as the signal SIGCHLD should not be handled by the execution monitor and should not be reported as an error. If you run the test cases now you'll get this compiler error for one test case: "../../../boost/asio/detail/socket_ops.hpp", line 218: Error: Cannot assign void* to char*. "../../../boost/asio/detail/socket_ops.hpp", line 229: Error: Cannot assign void* to char*. "../../../boost/asio/detail/descriptor_ops.hpp", line 66: Error: Cannot assign void* to char*. "../../../boost/asio/detail/descriptor_ops.hpp", line 72: Error: Cannot assign void* to char*. The bug has been reported to the Boost.Asio mailing list. If you want to build that one test case, too, you need to fix the two files in Boost.Asio 1.36.0 yourself. All the test cases can be built and run with: $ cd ~/boost_1_36_0/libs/process/test $ ../../../bjam --toolset=sun stdlib=sun-stlport -q

4 9

[Phoenix-3] Is Actor assignable?
by Michel MORIN 23 Jan '11

23 Jan '11

Hi, In Phoenix 3, is Actor assignable? This is necessary for filter_iterator/transform_iterator with Phoenix to be "neat" iterators. (Unfortunately, Actor is not assignable in Phoenix 2.) P.S. After writing this mail, I found this comment (What a coincidence ;-) #4853 (Actor is never assignable regardless of the template parameter) https://svn.boost.org/trac/boost/ticket/4853#comment:2 Comment (by theller): This is fixed in phoenix V3 So the answer to this question is YES. Thank you for great work, Thomas! Regards, Michel

3 18

[asio] cygwin issue
by vicente.botet 22 Jan '11

22 Jan '11

Hi, whiline runnin the asio tests (under cygwin gcc-4.3 Windows XP ) as follows bjam cxxflags="-D__USE_W32_SOCKETS -D_WIN32_WINNT=0x0501" I got a compile error ../../../boost/asio/detail/impl/win_iocp_io_service.ipp: In member function â?~void boost::asio::detail::win_iocp_io_service::do_add_timer_queue(boost::asio::detail::timer_queue_base&)â?T: ../../../boost/asio/detail/impl/win_iocp_io_service.ipp:461: error: no matching function for call to â?~boost::asio::detail::posix_thread::posix_thread(boost::asio::detail::win_iocp_io_service::timer_thread_function&, int)â?T ../../../boost/asio/detail/posix_thread.hpp:38: note: candidates are: boost::asio::detail::posix_thread::posix_thread(const boost::asio::detail::posix_thread&) I have changed the prototype as the one for win_thread and now all the tests are OK. posix_thread(Function f, unsigned int = 0); Best, Vicente

1 0

namespace boost?
by Robert Ramey 22 Jan '11

22 Jan '11

I'm doing a toy project which uses a lot of boost libraries. In the course of doing this, I'm reminded of something that has bugged me for a long time. That is the placement of lots of stuff inside the namespace boost. Now that boost is the size that it is, this can become are real barrier to making things understandable. Currently I'm looking at range and iterator libraries - but I'm no there are lots of offenders. Certain names like join, zip, map, copy, etc. ... apear in multiple libraries. I would like to use "using namespace boost" but then I'm afraid that using something like copy will be ambigiuos Could we agree that the boost namespace (and directory structure) only be used for library names. Some time ago, I caught hell for including just a couple of functions in boost/namespace and directory. But I see tons of stuff in there now. Robert Ramey

27 96

[geometry] fusion adapt is missing
by Akira.T 22 Jan '11

22 Jan '11

Hi, follow code in libs/geometry/example/c09_custom_fusion_example.cpp : #include <boost/geometry/geometries/adapted/fusion.hpp> #include <boost/geometry/geometries/adapted/fusion_cartesian.hpp> But, this header file is missing. Please add file to trunk. == Akira Takahashi Blog : http://d.hatena.ne.jp/faith_and_brave/

3 6

[1.44][serialization] Link error with polymorphic archive and BOOST_CLASS_EXPORT
by Wilson Tim-CTW024 21 Jan '11

21 Jan '11

I've run into a conflict between use of the polymorphic archives and the BOOST_CLASS_EXPORT() macro. It doesn't seem possible to use both without getting a link error. The following code illustrates the problem (yes, I know this code doesn't do anything worth doing, but it's the simplest code that demonstrates the problem): ---------------------- # include <sstream> # include <boost/serialization/export.hpp> # include <boost/archive/polymorphic_binary_oarchive.hpp> class A { public: template<class Archive> void serialize(Archive & ar, const unsigned version) { } }; BOOST_CLASS_EXPORT(A); int main() { A a; std::ostringstream os; boost::archive::polymorphic_binary_oarchive oa(os); oa & a; } ----------------------- This code compiles OK, but a link error is generated. I've put the full link error at the bottom of this post; the gist is an undefined reference to: boost::archive::detail::archive_serializer_map<boost::archive::detail::p olymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::ar chive::binary_oarchive, char, std::char_traits<char> > > >::erase(boost::archive::detail::basic_serializer const*) I can make the error go away by either: 1) Commenting out the BOOST_CLASS_EXPORT 2) Changing the type of the oarchive from polymorphic_binary_oarchive to binary_oarchive. It really looks like there's something missing from the serialization library related to the polymorphic oarchive. Thanks in advance for any help. Tim Wilson Full link error: ---------------- /tmp/ccQvudrk.o: In function `boost::archive::detail::pointer_oserializer<boost::archive::detail::pol ymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::arch ive::binary_oarchive, char, std::char_traits<char> > >, A>::pointer_oserializer()': test_boost_ser_main.cpp:(.text._ZN5boost7archive6detail19pointer_oserial izerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchive_implINS0_15b inary_oarchiveEcSt11char_traitsIcEEEEE1AEC2Ev[_ZN5boost7archive6detail19 pointer_oserializerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchi ve_implINS0_15binary_oarchiveEcSt11char_traitsIcEEEEE1AEC5Ev]+0x4f): undefined reference to `boost::archive::detail::archive_serializer_map<boost::archive::detail:: polymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::a rchive::binary_oarchive, char, std::char_traits<char> > > >::insert(boost::archive::detail::basic_serializer const*)' /tmp/ccQvudrk.o: In function `boost::archive::detail::pointer_oserializer<boost::archive::detail::pol ymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::arch ive::binary_oarchive, char, std::char_traits<char> > >, A>::~pointer_oserializer()': test_boost_ser_main.cpp:(.text._ZN5boost7archive6detail19pointer_oserial izerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchive_implINS0_15b inary_oarchiveEcSt11char_traitsIcEEEEE1AED2Ev[_ZN5boost7archive6detail19 pointer_oserializerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchi ve_implINS0_15binary_oarchiveEcSt11char_traitsIcEEEEE1AED5Ev]+0x24): undefined reference to `boost::archive::detail::archive_serializer_map<boost::archive::detail:: polymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::a rchive::binary_oarchive, char, std::char_traits<char> > > >::erase(boost::archive::detail::basic_serializer const*)' collect2: ld returned 1 exit status

2 2

[1.44][serialization] Link error with polymorphic archive and BOOST_CLASS_EXPORT
by Wilson Tim-CTW024 21 Jan '11

21 Jan '11

(Sorry if this is a duplicate post...I sent it once, didn't see it, so I'm sending again) I've run into a conflict between use of the polymorphic archives and the BOOST_CLASS_EXPORT() macro. It doesn't seem possible to use both without getting a link error. The following code illustrates the problem (yes, I know this code doesn't do anything worth doing, but it's the simplest code that demonstrates the problem): ---------------------- # include <sstream> # include <boost/serialization/export.hpp> # include <boost/archive/polymorphic_binary_oarchive.hpp> class A { public: template<class Archive> void serialize(Archive & ar, const unsigned version) { } }; BOOST_CLASS_EXPORT(A); int main() { A a; std::ostringstream os; boost::archive::polymorphic_binary_oarchive oa(os); oa & a; } ----------------------- This code compiles OK, but a link error is generated. I've put the full link error at the bottom of this post; the gist is an undefined reference to: boost::archive::detail::archive_serializer_map<boost::archive::detail::p olymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::ar chive::binary_oarchive, char, std::char_traits<char> > > >::erase(boost::archive::detail::basic_serializer const*) I can make the error go away by either: 1) Commenting out the BOOST_CLASS_EXPORT 2) Changing the type of the oarchive from polymorphic_binary_oarchive to binary_oarchive. It really looks like there's something missing from the serialization library related to the polymorphic oarchive. Thanks in advance for any help. Tim Wilson Full link error: ---------------- /tmp/ccQvudrk.o: In function `boost::archive::detail::pointer_oserializer<boost::archive::detail::pol ymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::arch ive::binary_oarchive, char, std::char_traits<char> > >, A>::pointer_oserializer()': test_boost_ser_main.cpp:(.text._ZN5boost7archive6detail19pointer_oserial izerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchive_implINS0_15b inary_oarchiveEcSt11char_traitsIcEEEEE1AEC2Ev[_ZN5boost7archive6detail19 pointer_oserializerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchi ve_implINS0_15binary_oarchiveEcSt11char_traitsIcEEEEE1AEC5Ev]+0x4f): undefined reference to `boost::archive::detail::archive_serializer_map<boost::archive::detail:: polymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::a rchive::binary_oarchive, char, std::char_traits<char> > > >::insert(boost::archive::detail::basic_serializer const*)' /tmp/ccQvudrk.o: In function `boost::archive::detail::pointer_oserializer<boost::archive::detail::pol ymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::arch ive::binary_oarchive, char, std::char_traits<char> > >, A>::~pointer_oserializer()': test_boost_ser_main.cpp:(.text._ZN5boost7archive6detail19pointer_oserial izerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchive_implINS0_15b inary_oarchiveEcSt11char_traitsIcEEEEE1AED2Ev[_ZN5boost7archive6detail19 pointer_oserializerINS1_26polymorphic_oarchive_routeINS0_20binary_oarchi ve_implINS0_15binary_oarchiveEcSt11char_traitsIcEEEEE1AED5Ev]+0x24): undefined reference to `boost::archive::detail::archive_serializer_map<boost::archive::detail:: polymorphic_oarchive_route<boost::archive::binary_oarchive_impl<boost::a rchive::binary_oarchive, char, std::char_traits<char> > > >::erase(boost::archive::detail::basic_serializer const*)' collect2: ld returned 1 exit status

2 1

[Process] List of small issues
by Artyom 21 Jan '11

21 Jan '11

Hello, I've made a micro review of Boost.Process, there are small issues I've found: - stream buffer implementation: underflow() you need to check the errno if it is EINTR, returning -1 and getting EINTR is not a problem and thus it should retry. sync(); Same as in underflow() - check for EINTR and retry, but also there is a problem that you do not check that you had fully written the data. For example what I write out << std::flush sync() is called and I expect the all data should be written to device, so if return value is less then the size of the buffer you should retry and write again till buffer is empty, you get error or EOF. - Windows and Unicode. You are using CreateProcessA. I would recommend to always use wide API and convert narrow strings to wide similarly to what boost::filesystem::v3 does, so for example where the global locale as utf-8 facet you would convert narrow strings to wide and run it. Notes: 1. You can also always assume that strings under windows are UTF-8 and always convert them to wide string before system calls. This is I think better approach, but it is different from what most of boost does. 2. I do not recommend adding wide API - makes the code much uglier, rather convert normal strigns to wide strings before system call. - It may be very good addition to implement full support of putback. Additional point: ----------------- I've noticed that you planned asynchronous notification and so on but I think it is quite important to add feature that provide an ability to wait for multiple processes to terminate and have timeout. It can be done using sigtimedwait/sigwait and assigned signal handlers for SIGCHLD Artyom P.S.: Good luck with the review library looks overall very nice.

21 144