Hi Oliver; To be honest, I have no idea why we are getting the linking error, but yes if defining your own local scope_array function stops the error , it's OK. This is debugging code so we can live with the duplicity.
FWIW, I noticed the build on linux is broken due to a checksum mismatch in the English dictionary :(. Pedro. >________________________________ > From: Oliver-Rainer Wittmann <orwittm...@googlemail.com> >To: ooo-dev@incubator.apache.org >Sent: Thursday, September 20, 2012 9:32 AM >Subject: Re: [code] building trunk, rev. 1386983 break in setup_native > >Hi, > >Hi, > > >On 19.09.2012 20:00, Oliver-Rainer Wittmann wrote: >>>> >>>> On 19.09.2012 08:44, Oliver-Rainer Wittmann wrote: >>>>> Hi, >>>>> >>>>> On 19.09.2012 04:50, Pedro Giffuni wrote: >>>>>> Hi again; >>>>>> >>>>>> I tried something in revision 1387438: basically I preserved some >>>>>> configuration changes from the previous patchset. >>>>>> >>>>> >>>>> Thanks >>>>> I will try. >>>>> >>>> >>>> The build with --enable-dbgutil still breaks in setup_native. >>>> >>> >>> I did a small cleanup of the FreeBSD specific patch but sadly, >>> I am afraid I ran out of my Windows-fu :(. >>> >>> I found this >>> http://cubicspot.blogspot.com/2007/06/solving-pesky-lnk2005-errors.html >>> >>> >>> I think it may be something really simple, but we need a Windows >>> expert here. >>> >>> It would be really sad to have to revert the update so I hope someone >>> steps in! >>> >> >> I do not think that it is needed to revert the boost update. >> The problem only occurs when building with --enable-dbgutil and it is quite >> easy >> to get rid of the boost::scoped_array usage in the corresponding small code >> snippet. >> > >Does the attached patch make sense in order to get rid of the problem by >removing the usage of boost::scoped_array? > >Thx in advance for your feedback. > >Best regards, Oliver. > > >
