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

Fwd: Boost.log file collector
by Daniel Krikun 22 Nov '13

22 Nov '13

Hello, When I set up text_file_backend with file rotation and a file collector with the target directory other from the directory where my application resides, then if the application crashes, the current log file will not be collected to the target directory. This is somewhat inconvenient, because, let's say we setup the file collector to collect all the log files under 'logs' subfolder, and then if the application crashes we ask the user to simply e-mail the 'logs' folder to see what possibly went wrong before the crash, but, alas, the most interesting piece is missing. Is there a way to work around the problem? Thanks,

1 0

[multiprecision] Empty intervals and intervals with NaN check
by Александров Петр 21 Nov '13

21 Nov '13

Hello. In MPFI documentation it is said that "MPFI functions operate on valid intervals ..., their behavior with non-valid intervals as input is undefined". Are intervals checked in Boost Multiprecision library whether they are invalid? Can this be easily done using Boost? Kind regards, Petr.

2 3

Problem with variadic BOOST_PP_TUPLE_REM in Clang
by Jeremiah Willcock 21 Nov '13

21 Nov '13

When using Clang version "Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)" in C++11 mode, the code: #include <boost/preprocessor.hpp> BOOST_PP_TUPLE_REM()(foo(bar, baz) const) is not expanded correctly. The second line expands to: BOOST_PP_TUPLE_REM_(foo(bar, baz) const) while on GCC 4.9, it expands to: foo(bar, baz) const Is there a known issue with this macro on Clang? -- Jeremiah Willcock

6 12

Re: [Boost-users] [BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 21 Nov '13

21 Nov '13

Thanks a lot for that. Problem solved, in terms of the function call. What remains is that my custom visitor is not behaving as I thought** it would! What I wanted to implement (which partially is based on an older thread that you replied) is cut-off radius around the source. The problem with my version of visitor is that it dies when it 'examines' the first vertex outside the radius, but this doesnt imply that everything within radium is correctly found (correct distances etc). Any tips about this? Thanks a lot

2 1

[BGL] visitors.hpp:138: error: no type named 'event_filter' in 'class dijkstra_custom_visitor'
by The Maschine 21 Nov '13

21 Nov '13

Hi, Im trying to use a custom visitor but I get this error. My custom visitor is: class dijkstra_custom_visitor : public boost::default_dijkstra_visitor { public: dijkstra_threshold(glm::dvec3 source, double threshold): s(source), threshold(threshold) {} struct hit_threshold {}; void examine_vertex(boost::graph_traits <unGraph>::vertex_descriptor v, const unGraph& g) { glm::dvec3 dest = boost::get(&VertexProperties::m_mid_point, g, v); if( glm::distance(s,dest) > threshold ) throw hit_threshold(); } double threshold; glm::dvec3 s; }; My 'calling' line is: std::vector<Vertex> predecessors(boost::num_vertices(m_ugraph)); std::vector<Weight> distances(boost::num_vertices(m_ugraph), std::numeric_limits<double>::max() ); IndexMap indexMap = boost::get(boost::vertex_index, m_ugraph); PredecessorMap predecessorMap(&predecessors[0], indexMap); DistanceMap distanceMap(&distances[0], indexMap); glm::dvec3 s_mid = m_ugraph[*vertex_iterator_begin].m_mid_point; double thres = 500.0f; boost::dijkstra_shortest_paths(m_ugraph, *vertex_iterator_begin, boost::predecessor_map(predecessorMap).distance_map(distanceMap).visitor(boost::make_dijkstra_visitor(dijkstra_custom_visitor(s_mid,thres)))); What do you think is the problem? thanks

2 1

TypeTraits like library for inheritance access specifiers?
by Mostafa 21 Nov '13

21 Nov '13

Is there a TypeTraits like library for determining inheritance access specificers? Something like a is_private_base_of? Thanks, Mostafa

1 0

linking with boost log 1.54
by Ovanes Markarian 20 Nov '13

20 Nov '13

Hi *, I am stuck with a problem to link on linux (ubuntu 12.04) with a boost log library (clang 3.0 & libstdc++). No matter what I do it fails. The problem is: I have a 3rd party library which is delivered as an .so-module and I need to link with it. My project is organized so that we develop static libraries and link them with test or application runner executables. I currently build boost as static libraries only, after I link my project with log library I get tons of errors like: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(nptl-init.o): In function `__pthread_initialize_minimal_internal': /build/buildd/eglibc-2.15/nptl/nptl-init.c:296: undefined reference to `__libc_setup_tls' /build/buildd/eglibc-2.15/nptl/nptl-init.c:314: undefined reference to `_dl_cpuclock_offset' /build/buildd/eglibc-2.15/nptl/nptl-init.c:430: undefined reference to `_dl_pagesize' /build/buildd/eglibc-2.15/nptl/nptl-init.c:456: undefined reference to `_dl_init_static_tls' /build/buildd/eglibc-2.15/nptl/nptl-init.c:458: undefined reference to `_dl_wait_lookup_done' /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(nptl-init.o): In function `__pthread_get_minstack': /build/buildd/eglibc-2.15/nptl/nptl-init.c:479: undefined reference to `_dl_pagesize' /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libpthread.a(pthread_create.o): In function `allocate_stack': /build/buildd/eglibc-2.15/nptl/allocatestack.c:457: undefined reference to `_dl_stack_flags' /build/buildd/eglibc-2.15/nptl/allocatestack.c:596: undefined reference to `_dl_stack_flags' /usr/local/lib/libboost_log-mt-s.a(text_file_backend.o): In function `boost::log::v2s_mt_posix::sinks::anonymous::file_collector::file_collector(boost::shared_ptr<boost::log::v2s_mt_posix::sinks::anonymous::file_collector_repository> const&, boost::filesystem::path const&, unsigned long, unsigned long)': libs/log/src/text_file_backend.cpp:(.text+0x60b): undefined reference to `boost::filesystem::detail::current_path(boost::system::error_code*)' libs/log/src/text_file_backend.cpp:(.text+0x65c): undefined reference to `boost::filesystem::absolute(boost::filesystem::path const&, boost::filesystem::path const&)' libs/log/src/text_file_backend.cpp:(.text+0x6b1): undefined reference to `boost::filesystem::detail::create_directories(boost::filesystem::path const&, boost::system::error_code*)' And so on. Do you have any hints or suggestions? Thanks, Ovanes

4 7

[String_Ref] Working with other parts of boost
by Norbert Wenzel 20 Nov '13

20 Nov '13

Hi, I wanted to play around with Boost.String_Ref and found some old code that I thought would be the ideal case for string_refs. It's basically a config file reader that stores the whole line and also a key/value pair that may be found in that line. So a single line looked something like this: std::string line; //original line as is in the file boost::string_ref key; //extracted key subpart boost::string_ref value; //extracted value subpart But when I wanted to trim the string_refs (eg. for lexical_casting them) I got compile errors, because boost::trim uses erase, which of course is not supported by string_ref. But string_ref has the remove_prefix/suffix member functions, which would be exactly what trim needs. So I quickly hacked an additional overload of trim_*_if that calls the remove_*fix instead of the .erase() member function and it seemed to work. The second problem occurred when I tried to extract my key/value pair from a line using the Tokenizer, which seems to be old, but it still works for simple cases. Tokenizer internally uses assign() to fill an internal buffer with the next token, which of course is no member function of string_ref. Since it seems Tokenizer only uses the assign version that takes two iterators it might be possible to add such an assign() function to string_ref. At least I added one as a testcase locally and it worked in my limited testcase. Are there any plans to add either trim() or Tokenizer support for string_ref? I'm not sure about the Tokenizer/assign stuff, since one would have to change string_ref but I really think the trim() support would be helpful. Anyway, these issues kept me from actually using string_ref, since the code did not compile (or required changes to boost headers in order to compile). And I did not want to redo some of the boost string algorithm stuff in order to use string_refs. Norbert

4 9

[Asio] Issues with kqueue_reactor, dynamic libraries and -fvisibility=hidden
by Andrei Bica 19 Nov '13

19 Nov '13

I'm having a problem with a larger project for MacOS which uses multiple dynamic libraries and asio features (deadline_timers and tcp/udp scokets). I've managed to reproduce my problem in the following minimal example: ////////// Timer.hpp ////////// #ifndef TIMER_HPP #define TIMER_HPP #include <boost/asio.hpp> #include <boost/thread.hpp> #define VISIBLE __attribute__ ((visibility ("default"))) class VISIBLE Timer { public: Timer(boost::asio::io_service& service); private: void onTimeout(const boost::system::error_code& code); boost::asio::deadline_timer timer; }; #endif // Timer_HPP ////////// Timer.cpp ////////// #include <Timer.hpp> Timer::Timer(boost::asio::io_service& service) : timer(service) { timer.expires_from_now(boost::posix_time::seconds(1)); timer.async_wait(boost::bind(&Timer::onTimeout, this, _1)); } void Timer::onTimeout(const boost::system::error_code& code) { std::cout << "The callback from the dynamic library was called." << std::endl; } ////////// main.cpp ////////// #include <Timer.hpp> boost::asio::io_service service; void run() { service.run(); } void onTimeout(const boost::system::error_code& code) { std::cout << "The callback from main was called." << std::endl; } int main() { Timer timer(service); boost::asio::deadline_timer deadline_timer(service); deadline_timer.expires_from_now(boost::posix_time::seconds(1)); deadline_timer.async_wait(boost::bind(&onTimeout, _1)); boost::thread t(boost::bind(&run)); t.join(); return 0; } Timer.cpp is compiled into a dynamic library and used by main.cpp which is compiled as an executable. The environment: MacOS 10.8.5, Boost 1.54.0, clang 500.2.79 The parameters which are passed to clang at compilation time are: clang++ -ggdb -c Timer.cpp -I. -I/opt/local/include -fPIC -fvisibility=hidden clang++ -ggdb -o libTimer.dylib -dynamiclib Timer.o -L/opt/local/lib -lboost_thread-mt -lboost_system-mt -fvisibility=hidden clang++ -ggdb main.cpp -o runTest -I. -I/opt/local/include -L. -L/opt/local/lib -lboost_thread-mt -lboost_system-mt -lTimer fvisibility=hidden As you can see the visibility is set to hidden at compilation time in order to expose only desired functions (e.g. the Timer class) from my library. The problem that arise is that the callback of the timer from main.cpp is never called. If I remove the visibility flag at compilation time the example works as it should (both timer callbacks are called). When I did further investigations I've observed that 2 kqueue_reactor instances are create when using hidden visibility and only one kqueue_reactor is created when visibility is set to default. I need an advise on how should I proceed so that I can still use the visibility set to hidden at compilation time but have the example working as expected. When compiling the example on Linux using visibility set to hidden the example works as expected. Regards, Andrei

1 0

Compiling Boost 1.55.0 with Intel 14.0.1 and libstdc++ from GCC 4.8.1
by Maxime Boissonneault 19 Nov '13

19 Nov '13

Hi, I am attempting to build Boost 1.55.0 with Intel compiler 14.0.1, using the Standard C++ Library provided by GCC 4.8.1 I am having a lot of errors with "fenv". Here is a subset of those errors, with one particular object that is being built by the build script. The offending command line is "icpc" -c -xc++ -w1 -inline-level=2 -O3 -ip -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_DLL -DBOOST_LOG_NO_THREADS -DBOOST_LOG_USE_AVX2 -DBOOST_LOG_USE_NATIVE_SYSLOG -DBOOST_LOG_USE_SSSE3 -DBOOST_LOG_WITHOUT_EVENT_LOG -DBOOST_SPIRIT_USE_PHOENIX_V3=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_DONT_USE_CHRONO=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "bin.v2/libs/log/build/intel-linux/release/log-api-unix/named_scope_format_parser.o" "libs/log/src/named_scope_format_parser.cpp" Errors are such as : In file included from ./boost/math/tools/promotion.hpp(26), from ./boost/math/special_functions/detail/round_fwd.hpp(12), from ./boost/math/special_functions/math_fwd.hpp(26), from ./boost/math/special_functions/fpclassify.hpp(19), from ./boost/spirit/home/support/detail/sign.hpp(22), from ./boost/spirit/home/karma/numeric/detail/numeric_utils.hpp(22), from ./boost/spirit/home/karma/numeric/uint.hpp(33), from ./boost/spirit/include/karma_uint.hpp(16), from libs/log/src/named_scope_format_parser.cpp(22): ./boost/math/tools/config.hpp(309): error: identifier "fexcept_t" is undefined fexcept_t m_flags; ^ In file included from ./boost/math/tools/promotion.hpp(26), from ./boost/math/special_functions/detail/round_fwd.hpp(12), from ./boost/math/special_functions/math_fwd.hpp(26), from ./boost/math/special_functions/fpclassify.hpp(19), from ./boost/spirit/home/support/detail/sign.hpp(22), from ./boost/spirit/home/karma/numeric/detail/numeric_utils.hpp(22), from ./boost/spirit/home/karma/numeric/uint.hpp(33), from ./boost/spirit/include/karma_uint.hpp(16), from libs/log/src/named_scope_format_parser.cpp(22): ./boost/math/tools/config.hpp(301): error: identifier "FE_INVALID" is undefined fegetexceptflag(&m_flags, FE_ALL_EXCEPT); I have the following set export CPLUS_INCLUDE_PATH=/software6/compilers/gcc/4.8.1/include/c++/4.8.1/ if I unset CPLUS_INCLUDE_PATH, this specific object compiles fine (with warnings, but no error). Does anyone have an idea of weither this is a bug with Intel compiler or with Boost ? Best regards, -- --------------------------------- Maxime Boissonneault Analyste de calcul - Calcul Québec, Université Laval Ph. D. en physique

3 6