To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111080





------- Additional comments from [email protected] Fri Apr 23 11:55:36 
+0000 2010 -------
@thb: ups sorry for not mentioning the build options I was using.
I built with

./configure  \
--with-use-shell=bash \
--enable-qadevooo  \
--enable-crashdump=yes  \
--enable-cairo  --with-system-cairo  \
--enable-opengl  \
--enable-dbus  \
--enable-kde --disable-kdeab  \
--enable-minimizer  \
--enable-presenter-console  \
--enable-pdfimport  \
--enable-wiki-publisher  \
--enable-report-builder \
--with-package-format="rpm"  \
--with-mingwin=i686-pc-mingw32-g++   \
--with-jdk-home=/opt/jdk  \
--with-lang="es"  \
--enable-graphite   \
--enable-kde4  --with-system-zlib \
--enable-verbose \
--disable-strip-solver --enable-dbgutil \
--enable-mysql-connector --with-system-mysql \
--enable-presenter-extra-ui --disable-binfilter 

So yes, --enable-verbose and --enable-dbgutil caused the build breaker.

http://svn.services.openoffice.org/opengrok/xref/DEV300_m77/canvas/source/vcl/ca
nvashelper_texturefill.cxx#703 already uses OSL_DEBUG_LEVEL

#if defined(VERBOSE) && OSL_DEBUG_LEVEL > 0

you could just drop the defined(VERBOSE) and increase the OSL_DEBUG_LEVEL if 
you 
do not want this code to be compiled in a NON-PRO build, IIRC configuring with -
-enable-dbgutil passes to the compiler 

-DDBG_UTIL -DOSL_DEBUG_LEVEL=1

so, for example:

#if OSL_DEBUG_LEVEL > 2

would be compiled if you explicitely build with:

build dbglevel=3

There are several of this in vcl for example:
http://svn.services.openoffice.org/opengrok/search?
q=%22OSL_DEBUG_LEVEL+%3E+2%22&defs=&refs=&path=vcl&hist=&project=/DEV300_m77


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to