Hi,
On 27.09.2012 21:54, Pedro Giffuni wrote:
Answering to myself ...
----- Original Message -----
From: Pedro Giffuni
...
Hi Ariel;
From: Ariel Constenla-Haile <arie...@apache.org>
On Thu, Sep 27, 2012 at 09:27:23AM -0700, Pedro Giffuni wrote:
The big question here, at least for me, is why a boost update causes
trouble to stlport and why it only affects Windows.
Google lead me to
http://boost.2283326.n4.nabble.com/Can-t-build-boost-1-48-with-STLport-5-2-1-td4372308.html
"My best guess is the /D_STLP_DEBUG define which enables enhanced
debugging magic (iterator validation etc.) which might not be binary
compatible with Boost."
Nice find! The debugging capabilities in stlport are indeed considered an
important advantage over other implementations. According to OpenGrok
we define that macro in STLport-4.5.patch and a bunch of other places.
Actually, the key definition is here:
http://svn.services.openoffice.org/opengrok/xref/Current%20(trunk)/solenv/inc/settings.mk#894
We already ignore USE_STLP_DEBUG for OS2. Should we add Windows to the list?
Not having CDEFS+=-D_STLP_DEBUG means that we will have no additional checking
stuff in a DEBUG=yes build. Right?
My current impression is the following:
- the new boost version makes more or different use of stl
- we are not building with the "right" compiler and link switches in DEBUG=yes
builds.
- the three needed adjustments to module setup_native, svtools and sw avoid the
build breakers. I am not sure, if they are only workaround
Best regards, Oliver.
