On Fri, Dec 13, 2013 at 6:04 AM, Herbert Duerr <h...@apache.org> wrote:
> Hi Kay, > > > On 13.12.2013 01:20, Kay Schenk wrote: > >> On Mon, Dec 9, 2013 at 10:29 AM, Kay Schenk <kay.sch...@gmail.com> wrote: >> >>> On Mon, Dec 9, 2013 at 5:29 AM, Herbert Duerr <h...@apache.org> wrote: >>> >>>> By the way I created an enhancement issue [1] for upgrading to the >>>> latest >>>> boost version. I also developed a patch that already works with my >>>> systems >>>> and attached it to that issue. >>>> >>>> [1] https://issues.apache.org/ooo/show_bug.cgi?id=123817 >>>> >>>> It would be interesting to know if that experimental patch to support >>>> the >>>> new boost version works better for e.g. our Solaris ports? Please test. >>>> Maybe upgrading to boost 1.55 is a good idea for the AOO 4.1 release. >>>> >>>> OK, good...I'll have a look soonish. >>> >> >> Well I applied this patch but decided to just continue with 1.54 (my >> local) >> instead of downloading 1.55, or using supplied supplied boost with the >> patch (I may try that next). >> >> My traceback... >> [...] >> >> /home/kschenk/AOO_source/main/solver/410/unxlngi6.pro/inc/ >> stl/hash_set:42:26: >> error: 'hash' is already declared in this scope >> > > AOO's "normal" boost has the hash template in the boost/tr1 namespace. We > need it in the std namespace though (like TR1's unordered containers), so > we map them from their original boost/tr1 namespace to the std namespace. > > In your installation the hash template is apparently already mapped to the > std namespace, so us trying to map it there again causes trouble. To verify > this idea you could comment out the > using STLP4_EMUBASE_NS::hash; > lines in booth main/stlport/systemstl/hash_* files. > a short update on my progress... The suggestion above worked for that problem... > > [...] >> >> The second one seems to center around the following from boost itself in >> -- >> In file included from /usr/include/boost/functional/hash/hash.hpp >> >> #if !defined(BOOST_HASH_NO_EXTENSIONS) \ >> && !defined(BOOST_FUNCTIONAL_HASH_EXTENSIONS_HPP) >> #include <boost/functional/hash/extensions.hpp> >> #endif >> >> so I don't know if we need to do something about BOOST_HASH_NO_EXTENSIONS >> > > That's a good idea. If we knew that the hash template was already > available in the std namespace then we wouldn't have to map it there > ourselves. Maybe one of these two boost configuration defines (or maybe the > BOOST_HASH_TR1_HASH define?) allow us to determine what your boost > installation needs to get us a nice hash template in the std namespace. > > > Herbert > I'm still working on the errors generated from the latter area... Thank you for all your help. > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- ------------------------------------------------------------------------------------------------- MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
