From Michael Stahl <mstahl@redhat.com>:
Michael Stahl has uploaded a new change for review.
Change subject: gbuild: disable symbols on --enable-dbgutil --disable-symbols
......................................................................
gbuild: disable symbols on --enable-dbgutil --disable-symbols
Due to the setup of gb_DEBUGLEVEL in gbuild.mk, gb_SYMBOL was always
enabled when --enable-dbgutil is set, with no way to override it.
Fix that by turning configure's ENABLE_SYMBOLS into a tri-state, where
the new "FALSE" value, set by an explicit --disable-symbols, overrides
any implicit way of enabling symbols.
But by default an --enable-dbgutil still enables gb_SYMBOL.
Change-Id: I94c609863980ed1ab9c73d7a4861c394442b531d
(cherry picked from commit d9cbc837f84c415f5949a6893764dae8268f0d85)
---
M berkeleydb/makefile.mk
M configure.in
M solenv/gbuild/gbuild.mk
M solenv/inc/settings.mk
4 files changed, 17 insertions(+), 9 deletions(-)
  git pull ssh://gerrit.libreoffice.org:29418/core refs/changes/72/572/1
--
To view, visit https://gerrit.libreoffice.org/572
To unsubscribe, visit https://gerrit.libreoffice.org/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: I94c609863980ed1ab9c73d7a4861c394442b531d
Gerrit-PatchSet: 1
Gerrit-Project: core
Gerrit-Branch: libreoffice-3-6
Gerrit-Owner: Michael Stahl <mstahl@redhat.com>
Context
- [PATCH] Change in core[libreoffice-3-6]: gbuild: disable symbols on	--enable-dbgutil --disable-symbol... · Gerrit
 
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.