Herbert,
Are you recommending that we use boost version 1_49 versus the one delivered with OpenOffice? If so, then we will reconfigure using the --with-system-boost flag. If we use 1_49, does it require any special configure / build steps? Today, we replaced the 1_48 version of emplace_args.hpp with the 1_49 version, then implemented the patch [2] and the issues below went away, but the compile complains about an undefined boost type on line 220 : BOOST_UNORDERED_CONSTRUCT_FROM_TUPLE(10, boost) We are thinking that we need to pull in another file from 1_49, but that may snowball into needing more files, but we are not sure. -----Original Message----- From: Herbert Duerr [mailto:h...@apache.org] Sent: Thursday, December 05, 2013 2:42 AM To: dev@openoffice.apache.org Cc: Meffe, David K; Steele, Raymond Subject: Re: EXTERNAL: Re: Building comphelper Hi Raymond, > Thanks Herbert. Do you have any idea why we would be receiving the following? > > Compiling: sal/rtl/source/unload.cxx > "/usr/local/include/boost/unordered/detail/emplace_args.hpp", line 199: > Error:Could not find a match for > boost::tuples::get<boost::tuples::N,boost::tuples::HT, > boost::tuples::TT>(constboost::tuples::tuple<boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type>) > needed > inboost::unordered::detail::construct_from_tuple<configmgr::Partial::Node,boost::tuples::null_type>(configmgr::Partial::Node*, > constboost::tuples::tuple<boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, > boost::tuples::null_type>&). > "/usr/local/include/boost/unordered/detail/emplace_args.hpp", line 350:Where: > While > instantiating"boost::unordered::detail::construct_from_tuple<configmgr::Partial::Node,boost::tuples::null_type>(configmgr::Partial::Node*, > constboost::tuples::tuple<boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, boost::tuples::null_type, > boost::tuples::null_type,boost::tuples::null_type, > boost::tuples::null_type>&)". > "/usr/local/include/boost/unordered/detail/emplace_args.hpp", line 350:Where: > Instantiated from > boost::unordered::unordered_map<rtl::OUString,configmgr::Partial::Node, > boost::hash<rtl::OUString>,_STL::equal_to<rtl::OUString>, > _STL::allocator<_STL::pair<const > rtl::OUString,configmgr::Partial::Node>>>::operator[](const rtl::OUString&). > "/opt/aoo-4.0.0/main/ sal/rtl/source/unload.cxx ", line 217: Where: > Instantiated from non-template code. Are you using the configure option --with-system-boost? If not, then the boost headers should be found in .../main/solenv/*/unx*/inc/boost/ and not in /usr/local/include/boost/ The top suspect for the actual problem you are seeing is a boost problem [1]. It was fixed in boost 1.49 with [2]. AOO is currently using boost 1.48 but problems such as this indicate that an update is overdue. [1] https://svn.boost.org/trac/boost/ticket/6784 [2] https://svn.boost.org/trac/boost/changeset/77972 Could you try to apply the patch [2] to the problematic boost header to check whether this solves the problem? If yes, we could apply it to our local boost header with the patch mechanism. Or even better we could update our boost libs, but that would eventually open another can of worms... Herbert
