February 2013 - Boost-users

Problem with boost 1.53 compilation in Windows
by DUNDEK Ivan 08 Feb '13

08 Feb '13

Hi. We are using boost in our project, and now with 1.53 and some added options we are unable to compile the boost in Windows. In Linux, the build is OK. It seems, that when compiling under Windows, the path for compiled boost obj files depends on the options specified, so if there are many options specified, the path become too long. With reduced number of options, the build is OK. Build environment: Windows7 64bit, Boost 1.53, VisualStudio 2010 Express Here is the build command: bjam -d2 --toolset=msvc-10.0 variant=debug,release threading=multi link=static runtime-link=shared install boost.locale.std=on boost.locale.icu=off boost.locale.winapi=off boost.locale.posix=off -a --with-log --with-thread --with-system --with-date_time --with-filesystem --with-program_options --with-iostreams --with-regex --with-serialization --with-locale --with-atomic define=BOOST_LOG_NO_SETTINGS_PARSERS_SUPPORT --prefix="c:\projects\cpce-cpp-stack\1.3.0\win" -sZLIB_SOURCE="c:\projects\cpce-cpp-stack\1.3.0\win\third-party\zlib-1.2.7" And the output: Performing configuration checks - iconv (libc) : no - iconv (separate) : no - has_icu builds : no Component configuration: - atomic : building - chrono : not building - context : not building - date_time : building - exception : not building - filesystem : building - graph : not building - graph_parallel : not building - iostreams : building - locale : building - log : building - math : not building - mpi : not building - program_options : building - python : not building - random : not building - regex : building - serialization : building - signals : not building - system : building - test : not building - thread : building - timer : not building - wave : not building ...patience... ...patience... ...patience... ...patience... ...found 30159 targets... ...updating 10944 targets... …. file bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj.rsp "libs\program_options\src\split.cpp" -Fo"bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj" -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_LOG_NO_SETTINGS_PARSERS_SUPPORT "-I." compile-c-c++ bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj.rsp" split.cpp failed to write output file 'bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\libboost_program_options-vc100-mt-gd-1_53.lib.rsp'! c:\projects\cpce-cpp-stack\1.3.0\src\boost_1_53_0>cd "c:\projects\cpce-cpp-stack\1.3.0\win" Thank you for advice Best regards Ivan Dundek.

2 2

Problem linking with boost 1, 51 64-bits from boostpro, VC10
by Alain Leblanc 07 Feb '13

07 Feb '13

Hi, I'm having some issues linking my code with the 64-bit version of boost 1.51 on windows with VC 10. I managed to write this small example that illustrates my problem. It is a project to create a DLL. I downloaded from boostpro.com. Here's the code: #include <boost/regex.hpp> #include <boost/filesystem.hpp> void useBoost() { } and the result. ------ Build started: Project: test-64, Configuration: Release x64 ------ UsesRegex.cpp UsesRegex.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)" (?system_category@system@boost@ @YAAEBVerror_category@12@XZ) UsesRegex.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::generic_category(void)" (?generic_category@system@boost@ @YAAEBVerror_category@12@XZ) C:\Users\aleblanc\projects\trunk\XDE\sandbox\alain\c-testing\test-64\x64\Release\test-64.dll : fatal error LNK1120: 2 unresolved externals ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== However, if I comment out the include for filesystem.hpp it compiles ok. I have included the path to the boost libraries in the 'Additional Library Directories' property for the linker. otherwise it complains about not finding the library for boost_regex. Compiling for 32 bit (with the path for the libraries to a 32-bit installation of boost) works fine. Any suggestion would be appreciated. Thanks, a

3 3

boost compiler warnings
by Dave Dyer 07 Feb '13

07 Feb '13

Using boost 52 on OSX / 64 and xcode 4, the new mac compiler produces a lot of "semantic issue" warnings. I assume these are all not consequential, but is this lint being addressed? The two issues it is complaining about is that "long" is compiled as int64, and that using string literals as char * is deprecated.

2 1

Serialization: BOOST_CLASS_EXPORT changes between 1.38 and 1.52
by Nathan Whitehorn 07 Feb '13

07 Feb '13

I'm upgrading a large data analysis project from boost 1.38 to 1.52 (see this 2008 Boostcon talk for details: http://www.icecube.umd.edu/~troy/talks/icefishing.pdf) Everything has gone remarkably smoothly, with a minimal degree of #if, except for one thing: a change in the semantics of BOOST_CLASS_EXPORT. The software is organized into a number of shared libraries each of which have serializable classes that generally inherit from a shared base class, through pointers to which the derived classes are almost always [de]serialized to/from a custom archive type. When using 1.38, the BOOST_CLASS_EXPORT directive was kept in the implementation file for each serializable class. This almost still works for 1.52 but can result in strange behavior that took me two days to track down. Some of our classes would report through unregistered class errors on [de]serialization. Which ones would depend on circumstances, compiler version, linker, and operating system. The reason turns out to be changes in handling of the class GUID. This is associated to the pointer serializer by BOOST_CLASS_EXPORT -- but also now apparently by the first instantiated code [de]serializing the class through that archive directly based on the presence of a template specialization of boost::serialization::guid<T>() currently in scope, which is NULL by default. Once NULL is set as the GUID, it stays that way, regardless of a proper BOOST_CLASS_EXPORT later. This occurred in our case as a result of def_pickle() calls in boost.python bindings that used the same classes and archive type. This can be fixed by BOOST_CLASS_EXPORT_KEY in all appropriate header files. Adding it is a sizeable amount of work (hundreds of classes) but I'm more concerned the mechanism is very fragile in the case of templates and I'm not sure what to do there. For example, we have a generic serializable container. Any specialization of it needs to be registered with BOOST_CLASS_EXPORT, which is fine, but anyone using that specialization needs to also include a header file BOOST_CLASS_EXPORT_KEY() in it for that particular specialization as well. In other words, you can't just use container<Foo> and expect it to work reliably and, moreover, if you use it *once* without having seen the right in-scope macro, it will break serialization of that type globally if you happen to have linked against a library that made this mistake. Probably. Depending on initialization order. So my questions: 1. Is it possible for things that would return GUIDs of NULL to try harder and look in a global registry instead of silently breaking things? This kind of global lookup was how 1.38 always worked and it seems considerably less fragile. 2. Is there a way to handle BOOST_CLASS_EXPORT_KEY() sanely in the case of templates without the risk of silent serialization failures -- in all instances of that class -- that depend on global initialization order? 3. Is it possible to change the GUID set in the extended type info object of a pointer_[i/o]serializer at runtime after the class has been added to the export registry? 4. Are there any suggested mechanisms for local hacks, given that we control the archive implementation, to implement 1-3 without changes to boost? -Nathan

2 3

[serialization] Support for Boost.Container?
by Jensen, Erik A 07 Feb '13

07 Feb '13

I see that Boost.Serialization has support for serializing STL containers, such as std::vector. However, I can't seem to serialize a boost::container::vector. Do I need to do something special to get this to work, or is it not supported? I need guaranteed support for incomplete types, so I can't use an STL vector. If it is not supported, what is my best bet, for now? Are there any plans to do so? Using Boost.Serialization with Boost.Container is something I would expect to just work, and it seems like most of the STL code could be reused. Thanks.

6 7

Re: [Boost-users] enable_shared_from_this()
by John M. Dlugosz 07 Feb '13

07 Feb '13

Frank Mori Hess<fmh6jj(a)gmail.com> wrote: > That means > throwing exceptions from the constructor after using shared_from_raw > (or in any derived constructor since ithe derived constructor would be > called later) causes bad things to happen. That's no different from stashing away a raw pointer from a constructor (e.g. passing it as a "parent" pointer to a referenced object). But that could be improved upon: The collaborators can be given a weak_ptr only. But, we may require that collaborators have owning references. In my library, a "borrower" (weak_ptr) could optionally hold a strong reference as well, so the reference could be upgraded from weak to strong after a point of commitment is reached. If there were some kind of on-spec pending ptr type, they could be seen as strong references eventually and in normal use, but automatically cleared or committed by the Create wrapper. That is, you would not have to keep track of the collaborators and hook them up in a second stage; rather, all such pending ptrs would become solid (wherever they are) with one call made after the ctor is golden. I never had a problem with it, though. —John

1 0

Re: [Boost-users] How do you compile Boost C++ code in Ubuntu?
by Giovanni 07 Feb '13

07 Feb '13

Greetings, I am sorry for the confusion; I mean my code that uses Boost C++ Libraries. I had set the shell variable $LD_LIBRARY_PATH to: /usr/lib/libboost_system.so. It was originally empty. I used the "echo" command to reflect the path that I had set it to. I had installed it with Ubuntu Software Center. Here is a snippet of: /usr/lib -rw-r--r-- 1 root root 31152 Jan 5 2012 libboost_chrono.so.1.48.0 -rw-r--r-- 1 root root 68216 Jan 2 2012 libboost_date_time.so.1.46.1 -rw-r--r-- 1 root root 122280 Jan 2 2012 libboost_filesystem.so.1.46.1 -rw-r--r-- 1 root root 324192 Jan 2 2012 libboost_graph.so.1.46.1 -rw-r--r-- 1 root root 328328 Jan 5 2012 libboost_graph.so.1.48.0 -rw-r--r-- 1 root root 101592 Jan 2 2012 libboost_iostreams.so.1.46.1 -rw-r--r-- 1 root root 885000 Jan 5 2012 libboost_locale.so.1.48.0 -rw-r--r-- 1 root root 105264 Jan 2 2012 libboost_math_c99f.so.1.46.1 -rw-r--r-- 1 root root 109264 Jan 2 2012 libboost_math_c99l.so.1.46.1 -rw-r--r-- 1 root root 109312 Jan 2 2012 libboost_math_c99.so.1.46.1 -rw-r--r-- 1 root root 265088 Jan 2 2012 libboost_math_tr1f.so.1.46.1 -rw-r--r-- 1 root root 244536 Jan 2 2012 libboost_math_tr1l.so.1.46.1 -rw-r--r-- 1 root root 240440 Jan 2 2012 libboost_math_tr1.so.1.46.1 -rw-r--r-- 1 root root 89656 Jan 3 2012 libboost_mpi_python-py27.so.1.46.1 -rw-r--r-- 1 root root 89656 Jan 3 2012 libboost_mpi_python-py32.so.1.46.1 -rw-r--r-- 1 root root 180320 Jan 3 2012 libboost_mpi.so.1.46.1 -rw-r--r-- 1 root root 180320 Jan 5 2012 libboost_mpi.so.1.48.0 -rw-r--r-- 1 root root 116720 Jan 5 2012 libboost_prg_exec_monitor.a lrwxrwxrwx 1 root root 27 Jan 5 2012 libboost_prg_exec_monitor-mt.a -> libboost_prg_exec_monitor.a lrwxrwxrwx 1 root root 35 Jan 5 2012 libboost_prg_exec_monitor-mt.so -> libboost_prg_exec_monitor.so.1.48.0 lrwxrwxrwx 1 root root 35 Jan 5 2012 libboost_prg_exec_monitor.so -> libboost_prg_exec_monitor.so.1.48.0 -rw-r--r-- 1 root root 56352 Jan 2 2012 libboost_prg_exec_monitor.so.1.46.1 -rw-r--r-- 1 root root 56352 Jan 5 2012 libboost_prg_exec_monitor.so.1.48.0 -rw-r--r-- 1 root root 414280 Jan 2 2012 libboost_program_options.so.1.46.1 -rw-r--r-- 1 root root 311168 Jan 2 2012 libboost_python-py27.so.1.46.1 -rw-r--r-- 1 root root 315264 Jan 5 2012 libboost_python-py27.so.1.48.0 -rw-r--r-- 1 root root 307072 Jan 2 2012 libboost_python-py32.so.1.46.1 -rw-r--r-- 1 root root 311136 Jan 5 2012 libboost_python-py32.so.1.48.0 -rw-r--r-- 1 root root 10472 Jan 2 2012 libboost_random.so.1.46.1 -rw-r--r-- 1 root root 1054456 Jan 2 2012 libboost_regex.so.1.46.1 -rw-r--r-- 1 root root 1079096 Jan 5 2012 libboost_regex.so.1.48.0 -rw-r--r-- 1 root root 1240020 Jan 5 2012 libboost_serialization.a lrwxrwxrwx 1 root root 24 Jan 5 2012 libboost_serialization-mt.a -> libboost_serialization.a lrwxrwxrwx 1 root root 32 Jan 5 2012 libboost_serialization-mt.so -> libboost_serialization.so.1.48.0 lrwxrwxrwx 1 root root 32 Jan 5 2012 libboost_serialization.so -> libboost_serialization.so.1.48.0 -rw-r--r-- 1 root root 446584 Jan 2 2012 libboost_serialization.so.1.46.1 -rw-r--r-- 1 root root 446584 Jan 5 2012 libboost_serialization.so.1.48.0 -rw-r--r-- 1 root root 80600 Jan 2 2012 libboost_signals.so.1.46.1 -rw-r--r-- 1 root root 14568 Jan 2 2012 libboost_system.so.1.46.1 -rw-r--r-- 1 root root 14568 Jan 5 2012 libboost_system.so.1.48.0 -rw-r--r-- 1 root root 1635110 Jan 5 2012 libboost_test_exec_monitor.a lrwxrwxrwx 1 root root 28 Jan 5 2012 libboost_test_exec_monitor-mt.a -> libboost_test_exec_monitor.a -rw-r--r-- 1 root root 101304 Jan 2 2012 libboost_thread.so.1.46.1 -rw-r--r-- 1 root root 109536 Jan 5 2012 libboost_thread.so.1.48.0 -rw-r--r-- 1 root root 33102 Jan 5 2012 libboost_timer.a lrwxrwxrwx 1 root root 16 Jan 5 2012 libboost_timer-mt.a -> libboost_timer.a lrwxrwxrwx 1 root root 24 Jan 5 2012 libboost_timer-mt.so -> libboost_timer.so.1.48.0 lrwxrwxrwx 1 root root 24 Jan 5 2012 libboost_timer.so -> libboost_timer.so.1.48.0 -rw-r--r-- 1 root root 18832 Jan 5 2012 libboost_timer.so.1.48.0 -rw-r--r-- 1 root root 1879526 Jan 5 2012 libboost_unit_test_framework.a lrwxrwxrwx 1 root root 30 Jan 5 2012 libboost_unit_test_framework-mt.a -> libboost_unit_test_framework.a lrwxrwxrwx 1 root root 38 Jan 5 2012 libboost_unit_test_framework-mt.so -> libboost_unit_test_framework.so.1.48.0 lrwxrwxrwx 1 root root 38 Jan 5 2012 libboost_unit_test_framework.so -> libboost_unit_test_framework.so.1.48.0 -rw-r--r-- 1 root root 656824 Jan 2 2012 libboost_unit_test_framework.so.1.46.1 -rw-r--r-- 1 root root 669080 Jan 5 2012 libboost_unit_test_framework.so.1.48.0 -rw-r--r-- 1 root root 1320168 Jan 2 2012 libboost_wave.so.1.46.1 -rw-r--r-- 1 root root 845962 Jan 5 2012 libboost_wserialization.a lrwxrwxrwx 1 root root 25 Jan 5 2012 libboost_wserialization-mt.a -> libboost_wserialization.a lrwxrwxrwx 1 root root 33 Jan 5 2012 libboost_wserialization-mt.so -> libboost_wserialization.so.1.48.0 lrwxrwxrwx 1 root root 33 Jan 5 2012 libboost_wserialization.so -> libboost_wserialization.so.1.48.0 -rw-r--r-- 1 root root 323128 Jan 2 2012 libboost_wserialization.so.1.46.1 -rw-r--r-- 1 root root 323128 Jan 5 2012 libboost_wserialization.so.1.48.0 Here is a listing of the files in: /usr/include/boost Go Bears >ls -al total 1308 drwxr-xr-x 86 root root 12288 Feb 7 03:51 . drwxr-xr-x 121 root root 20480 Feb 7 03:50 .. drwxr-xr-x 5 root root 4096 Feb 7 03:50 accumulators drwxr-xr-x 3 root root 4096 Feb 7 03:50 algorithm -rw-r--r-- 1 root root 4297 Jan 5 2012 aligned_storage.hpp -rw-r--r-- 1 root root 6505 Jan 5 2012 any.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:51 archive -rw-r--r-- 1 root root 15525 Jan 5 2012 array.hpp drwxr-xr-x 9 root root 4096 Feb 7 03:50 asio -rw-r--r-- 1 root root 4265 Jan 5 2012 asio.hpp -rw-r--r-- 1 root root 4120 Jan 5 2012 assert.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 assign -rw-r--r-- 1 root root 614 Jan 5 2012 assign.hpp drwxr-xr-x 9 root root 4096 Feb 7 03:51 bimap -rw-r--r-- 1 root root 387 Jan 5 2012 bimap.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 bind -rw-r--r-- 1 root root 581 Jan 5 2012 bind.hpp -rw-r--r-- 1 root root 618 Jan 5 2012 blank_fwd.hpp -rw-r--r-- 1 root root 1946 Jan 5 2012 blank.hpp -rw-r--r-- 1 root root 773 Jan 5 2012 call_traits.hpp -rw-r--r-- 1 root root 4455 Jan 5 2012 cast.hpp -rw-r--r-- 1 root root 4173 Jan 5 2012 cerrno.hpp -rw-r--r-- 1 root root 1589 Jan 5 2012 checked_delete.hpp drwxr-xr-x 4 root root 4096 Feb 7 03:50 chrono -rw-r--r-- 1 root root 706 Jan 5 2012 chrono.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 circular_buffer -rw-r--r-- 1 root root 1157 Jan 5 2012 circular_buffer_fwd.hpp -rw-r--r-- 1 root root 2540 Jan 5 2012 circular_buffer.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 compatibility -rw-r--r-- 1 root root 801 Jan 5 2012 compressed_pair.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 concept -rw-r--r-- 1 root root 23671 Jan 5 2012 concept_archetype.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 concept_check -rw-r--r-- 1 root root 32100 Jan 5 2012 concept_check.hpp drwxr-xr-x 7 root root 4096 Feb 7 03:51 config -rw-r--r-- 1 root root 2074 Jan 5 2012 config.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 container -rw-r--r-- 1 root root 33373 Jan 5 2012 crc.hpp -rw-r--r-- 1 root root 721 Jan 5 2012 cregex.hpp -rw-r--r-- 1 root root 17287 Jan 5 2012 cstdint.hpp -rw-r--r-- 1 root root 1739 Jan 5 2012 cstdlib.hpp -rw-r--r-- 1 root root 1511 Jan 5 2012 current_function.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:50 date_time -rw-r--r-- 1 root root 587 Jan 5 2012 date_time.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 detail drwxr-xr-x 2 root root 4096 Feb 7 03:50 dynamic_bitset -rw-r--r-- 1 root root 675 Jan 5 2012 dynamic_bitset_fwd.hpp -rw-r--r-- 1 root root 560 Jan 5 2012 dynamic_bitset.hpp -rw-r--r-- 1 root root 530 Jan 5 2012 enable_shared_from_this.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 exception -rw-r--r-- 1 root root 434 Jan 5 2012 exception.hpp -rw-r--r-- 1 root root 374 Jan 5 2012 exception_ptr.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:50 filesystem -rw-r--r-- 1 root root 1340 Jan 5 2012 filesystem.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 flyweight -rw-r--r-- 1 root root 622 Jan 5 2012 flyweight.hpp -rw-r--r-- 1 root root 2198 Jan 5 2012 foreach_fwd.hpp -rw-r--r-- 1 root root 45365 Jan 5 2012 foreach.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 format -rw-r--r-- 1 root root 2179 Jan 5 2012 format.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 function drwxr-xr-x 4 root root 4096 Feb 7 03:50 functional -rw-r--r-- 1 root root 18893 Jan 5 2012 functional.hpp -rw-r--r-- 1 root root 791 Jan 5 2012 function_equal.hpp -rw-r--r-- 1 root root 2200 Jan 5 2012 function.hpp -rw-r--r-- 1 root root 1574 Jan 5 2012 function_output_iterator.hpp drwxr-xr-x 4 root root 4096 Feb 7 03:51 function_types drwxr-xr-x 13 root root 4096 Feb 7 03:51 fusion -rw-r--r-- 1 root root 1859 Jan 5 2012 generator_iterator.hpp drwxr-xr-x 13 root root 4096 Feb 7 03:50 geometry -rw-r--r-- 1 root root 704 Jan 5 2012 geometry.hpp -rw-r--r-- 1 root root 921 Jan 5 2012 get_pointer.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 gil drwxr-xr-x 7 root root 12288 Feb 7 03:50 graph drwxr-xr-x 6 root root 4096 Feb 7 03:50 icl -rw-r--r-- 1 root root 794 Jan 5 2012 implicit_cast.hpp -rw-r--r-- 1 root root 1039 Jan 5 2012 indirect_reference.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:51 integer -rw-r--r-- 1 root root 4617 Jan 5 2012 integer_fwd.hpp -rw-r--r-- 1 root root 10877 Jan 5 2012 integer.hpp -rw-r--r-- 1 root root 8714 Jan 5 2012 integer_traits.hpp drwxr-xr-x 11 root root 4096 Feb 7 03:51 interprocess drwxr-xr-x 3 root root 4096 Feb 7 03:50 intrusive -rw-r--r-- 1 root root 499 Jan 5 2012 intrusive_ptr.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 io -rw-r--r-- 1 root root 2381 Jan 5 2012 io_fwd.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:51 iostreams -rw-r--r-- 1 root root 634 Jan 5 2012 is_placeholder.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 iterator -rw-r--r-- 1 root root 466 Jan 5 2012 iterator_adaptors.hpp -rw-r--r-- 1 root root 1983 Jan 5 2012 iterator.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 lambda -rw-r--r-- 1 root root 1271 Jan 5 2012 last_value.hpp -rw-r--r-- 1 root root 75248 Jan 5 2012 lexical_cast.hpp -rw-r--r-- 1 root root 6119 Jan 5 2012 limits.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 locale -rw-r--r-- 1 root root 887 Jan 5 2012 locale.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:51 logic -rw-r--r-- 1 root root 484 Jan 5 2012 make_shared.hpp drwxr-xr-x 10 root root 4096 Feb 7 03:50 math -rw-r--r-- 1 root root 2527 Jan 5 2012 math_fwd.hpp -rw-r--r-- 1 root root 596 Jan 5 2012 mem_fn.hpp -rw-r--r-- 1 root root 1273 Jan 5 2012 memory_order.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 move drwxr-xr-x 5 root root 4096 Feb 7 03:50 mpi -rw-r--r-- 1 root root 1101 Jan 5 2012 mpi.hpp drwxr-xr-x 10 root root 12288 Feb 7 03:50 mpl drwxr-xr-x 5 root root 4096 Feb 7 03:50 msm drwxr-xr-x 2 root root 4096 Feb 7 03:50 multi_array -rw-r--r-- 1 root root 15351 Jan 5 2012 multi_array.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 multi_index -rw-r--r-- 1 root root 3794 Jan 5 2012 multi_index_container_fwd.hpp -rw-r--r-- 1 root root 33455 Jan 5 2012 multi_index_container.hpp -rw-r--r-- 1 root root 1296 Jan 5 2012 next_prior.hpp -rw-r--r-- 1 root root 1014 Jan 5 2012 noncopyable.hpp -rw-r--r-- 1 root root 595 Jan 5 2012 nondet_random.hpp -rw-r--r-- 1 root root 773 Jan 5 2012 none.hpp -rw-r--r-- 1 root root 605 Jan 5 2012 none_t.hpp -rw-r--r-- 1 root root 619 Jan 5 2012 non_type.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:50 numeric -rw-r--r-- 1 root root 38818 Jan 5 2012 operators.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 optional -rw-r--r-- 1 root root 528 Jan 5 2012 optional.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 parameter -rw-r--r-- 1 root root 724 Jan 5 2012 parameter.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 pending drwxr-xr-x 12 root root 4096 Feb 7 03:51 phoenix -rw-r--r-- 1 root root 476 Jan 5 2012 phoenix.hpp -rw-r--r-- 1 root root 1821 Jan 5 2012 pointee.hpp -rw-r--r-- 1 root root 1124 Jan 5 2012 pointer_cast.hpp -rw-r--r-- 1 root root 1199 Jan 5 2012 pointer_to_other.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 polygon drwxr-xr-x 3 root root 4096 Feb 7 03:50 pool drwxr-xr-x 19 root root 4096 Feb 7 03:50 preprocessor -rw-r--r-- 1 root root 486 Jan 5 2012 preprocessor.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 program_options -rw-r--r-- 1 root root 819 Jan 5 2012 program_options.hpp -rw-r--r-- 1 root root 5510 Jan 5 2012 progress.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 property_map drwxr-xr-x 3 root root 4096 Feb 7 03:51 property_tree drwxr-xr-x 6 root root 4096 Feb 7 03:50 proto drwxr-xr-x 3 root root 4096 Feb 7 03:50 ptr_container drwxr-xr-x 6 root root 4096 Feb 7 03:51 python -rw-r--r-- 1 root root 2868 Jan 5 2012 python.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 random -rw-r--r-- 1 root root 3644 Jan 5 2012 random.hpp drwxr-xr-x 6 root root 4096 Feb 7 03:50 range -rw-r--r-- 1 root root 842 Jan 5 2012 range.hpp drwxr-xr-x 4 root root 4096 Feb 7 03:51 ratio -rw-r--r-- 1 root root 349 Jan 5 2012 ratio.hpp -rw-r--r-- 1 root root 19603 Jan 5 2012 rational.hpp -rw-r--r-- 1 root root 3926 Jan 5 2012 ref.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:50 regex -rw-r--r-- 1 root root 693 Jan 5 2012 regex_fwd.hpp -rw-r--r-- 1 root root 2174 Jan 5 2012 regex.h -rw-r--r-- 1 root root 823 Jan 5 2012 regex.hpp -rw-r--r-- 1 root root 502 Jan 5 2012 scoped_array.hpp -rw-r--r-- 1 root root 491 Jan 5 2012 scoped_ptr.hpp -rw-r--r-- 1 root root 9936 Jan 5 2012 scope_exit.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 serialization -rw-r--r-- 1 root root 552 Jan 5 2012 shared_array.hpp -rw-r--r-- 1 root root 2007 Jan 5 2012 shared_container_iterator.hpp -rw-r--r-- 1 root root 539 Jan 5 2012 shared_ptr.hpp -rw-r--r-- 1 root root 12795 Jan 5 2012 signal.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 signals drwxr-xr-x 3 root root 4096 Feb 7 03:50 signals2 -rw-r--r-- 1 root root 752 Jan 5 2012 signals2.hpp -rw-r--r-- 1 root root 345 Jan 5 2012 signals.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 smart_ptr -rw-r--r-- 1 root root 892 Jan 5 2012 smart_ptr.hpp drwxr-xr-x 17 root root 4096 Feb 7 03:50 spirit -rw-r--r-- 1 root root 1085 Jan 5 2012 spirit.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:50 statechart -rw-r--r-- 1 root root 5244 Jan 5 2012 static_assert.hpp -rw-r--r-- 1 root root 3391 Jan 5 2012 strong_typedef.hpp -rw-r--r-- 1 root root 287 Jan 5 2012 swap.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:51 system drwxr-xr-x 7 root root 4096 Feb 7 03:51 test drwxr-xr-x 5 root root 4096 Feb 7 03:51 thread -rw-r--r-- 1 root root 839 Jan 5 2012 thread.hpp -rw-r--r-- 1 root root 2652 Jan 5 2012 throw_exception.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 timer -rw-r--r-- 1 root root 2663 Jan 5 2012 timer.hpp -rw-r--r-- 1 root root 19728 Jan 5 2012 token_functions.hpp -rw-r--r-- 1 root root 3742 Jan 5 2012 token_iterator.hpp -rw-r--r-- 1 root root 2783 Jan 5 2012 tokenizer.hpp drwxr-xr-x 4 root root 4096 Feb 7 03:50 tr1 drwxr-xr-x 3 root root 4096 Feb 7 03:51 tuple -rw-r--r-- 1 root root 481 Jan 5 2012 type.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:51 typeof drwxr-xr-x 4 root root 12288 Feb 7 03:51 type_traits -rw-r--r-- 1 root root 4264 Jan 5 2012 type_traits.hpp drwxr-xr-x 6 root root 4096 Feb 7 03:51 units drwxr-xr-x 3 root root 4096 Feb 7 03:50 unordered -rw-r--r-- 1 root root 550 Jan 5 2012 unordered_map.hpp -rw-r--r-- 1 root root 550 Jan 5 2012 unordered_set.hpp drwxr-xr-x 3 root root 4096 Feb 7 03:51 utility -rw-r--r-- 1 root root 739 Jan 5 2012 utility.hpp drwxr-xr-x 2 root root 4096 Feb 7 03:50 uuid drwxr-xr-x 3 root root 4096 Feb 7 03:50 variant -rw-r--r-- 1 root root 883 Jan 5 2012 variant.hpp -rw-r--r-- 1 root root 1124 Jan 5 2012 version.hpp -rw-r--r-- 1 root root 719 Jan 5 2012 visit_each.hpp drwxr-xr-x 5 root root 4096 Feb 7 03:50 wave -rw-r--r-- 1 root root 926 Jan 5 2012 wave.hpp -rw-r--r-- 1 root root 474 Jan 5 2012 weak_ptr.hpp drwxr-xr-x 4 root root 4096 Feb 7 03:50 xpressive Go Bears >pwd /usr/include/boost I may be terribly wrong, but I believe that I have already installed Boost C++ Libraries. When I followed your instructions to install it (again), I couldn't. Here is the transcript from the Terminal. Go Bears >sudo apt-get install libboost-system-dev [sudo] password for arvind: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libboost-system-dev : Depends: libboost-system1.46-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. Go Bears > Can you please kindly tell me where did I go wrong, and what is wrong? Can you also please kindly tell me how can I compile my C++ code that uses Boost C++ Libraries? Thank you very much, and have an awesome day! Regards On Thu, Feb 7, 2013 at 6:18 AM, Mateusz Loskot <mateusz(a)loskot.net> wrote: > On 7 February 2013 10:06, Giovanni <giovanni.ong(a)comsoc.org> wrote: >> Greetings, >> I cannot compile my Boost C++ code. > > Do you mean Boost C++ code, thus building Boost libraries, > or you mean your code that *uses* Boost libraries? Unclear. > >> Initially, it complains of “undefined reference”. When I try to >> resolve this by including the library, I get the "/usr/bin/ld: cannot >> find -lboost_system" error. > > So, looks like the former, you are trying to use the libraries. > >> From the Terminal: >> Go Bears >echo $LD_LIBRARY_PATH >> /usr/lib/libboost_system.so > > Where do you get this from? > > "LD_LIBRARY_PATH, which is a colon-separated list of directories" [1] > > [1] http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html > >> Go Bears >make all >> g++ -L/usr/lib -lboost_system get_sys_info.cpp > > Have you installed it first? > > sudo apt-get install libboost-system-dev > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net

2 1

Problem linking to serialisation library on Mac OSX
by Tim Burgess 07 Feb '13

07 Feb '13

Hi, I built my boost on Mac OSX 10.8 as follows: ./bootstrap.sh -prefix=/users/tim/developer/libraries/boost_1_50_0/stage ./b2 -address-model=32_64 stdlib=libc++ This ran boost.build with the Darwin toolset, as expected, and generated no errors. Checking the stage/lib folder revealed a complete set of static and dynamic library files with appropriate date-time stamps. I specified the linker as libc++ as the project I'm working on using XCode 4.6 uses wxWidgets 2.9.4, which requires that the project be compiled using Apple's GCC instead of the default compiler (this, in turn, means that libc++ becomes the linker used by the project). However, when I try to build my XCode project, I get errors of the form: Undefined symbols for architecture x86_64: "boost::archive::basic_xml_iarchive<boost::archive::xml_wiarchive>::load_sta rt(char All of the errors refer to boost::archive or boost::serialisation. My project also uses the boost FileSystem, IOStream and System libraries, which don't generate any errors. I've found an awful lot of references to this issue on the web (particularly StackOverflow), but have yet to find an answer/solution. I'm pretty sure that I'm using the correct command-line options (I didn't specify architecture=combined, as Mac OSX SDK 10.8 no longer supports PPC), but I'm confused by the plethora of available build options, as I'm a novice on this platform. The project is a cross-platform effort and the same source code presented to my Windows VS2010 32/64-bit project builds and runs. Similarly, the same project built and ran under Mac OSX 10.6 with XCode 3.6 - I'd gladly revert to the older Mac O/S and XCode except for the fact that I'm a blind developer and the debugger provided in XCode 3.6 is not accessible to me using Apple's VoiceOver speech output utility (the debugger in XCode 4.6 holds out more hope for being usable). I'd greatly appreciate any tips and tricks for resolving this problem, so many thanks in advance. Best wishes. Tim Burgess Raised Bar Ltd. Tel: +44 (0)1827 719822 Web: http://www.raisedbar.net We can supply Roland and Avid products with specialist pre and post-sales support for visually-impaired users - just drop us a line for a quote. Don't forget to sign our on-line petition to lobby for improved access to music education and music technology at: http://www.raisedbar.net/petition.htm

1 0

Re: [Boost-users] enable_shared_from_this()
by John M. Dlugosz 07 Feb '13

07 Feb '13

On 2/5/2013 9:43 AM, boost-users-request-at-lists.boost.org |Boost/Allow to home| wrote: From: Dominique Devienne<ddevienne(a)gmail.com> > Thanks for any insight on this. Could very well be I'm missing > something obvious (my C++ expertise doesn't rise to Boost levels), but > so far I fail to see the drawbacks. My old smart pointers (dating back to the '90's) had full support for initializing a smart pointer from a raw pointer even if it was already known to the smart pointer system. It was one of six _essential_ features (I called it “lost and found”) and I agree there were no troubles with it. It is easy to do when the class is derived from a helper base (like enable_shared_from_this does) and furthermore it doesn't need the CRTP. I agree that an extension to the now-standard enable_self_from_this could be implemented that gives a self_from_this that may be called during the constructor or as the first way to obtain a shared_ptr, also provide for "lost and found" usage, and not behave differently for any usage that is well-formed using the standard class (that is, it would be a pure extension). When changing some existing code to use shared_ptr, I've wished something like that was available, and missed my old class in this respect. For new code, in general use a Create static member that wraps the call to the (private) constructor so you can't create anything other than a shared_ptr, and the stuff that needs the shared ptr during "construction" gets moved to the stage 2, in the body of Create. In particular, if the object registers itself with collaborators (via shared pointers) you really wanted that part _in_ the constructor. —John

2 1

How do you compile Boost C++ code in Ubuntu?
by Giovanni 07 Feb '13

07 Feb '13

Greetings, I cannot compile my Boost C++ code. Initially, it complains of “undefined reference”. When I try to resolve this by including the library, I get the "/usr/bin/ld: cannot find -lboost_system" error. From the Terminal: Go Bears >echo $LD_LIBRARY_PATH /usr/lib/libboost_system.so Go Bears >make all g++ -L/usr/lib -lboost_system get_sys_info.cpp /usr/bin/ld: cannot find -lboost_system collect2: ld returned 1 exit status make: *** [all] Error 1 Go Bears > Do you know what stupid mistakes did I make? >From my Makefile: all: g++ -L/usr/lib -lboost_system get_sys_info.cpp ./a.out Thank you so much, and have an awesome day!

2 1