On Mon, Nov 22, 2010 at 10:38:31PM +0100, Miklos Vajna <vmiklos@frugalware.org> wrote:
Does anyone have an idea when (and why) this changed, and what's the new way of getting the OSL_TRACE() output?
Oh, I guess this is related to David's recent 47d0946 in bootstrap.git. The attached patch fixes the problem for me - David, OK to push? Thanks.
From ada7e2409a039284e0f9f5c08da4b97e5bee0012 Mon Sep 17 00:00:00 2001 From: Miklos Vajna <vmiklos@frugalware.org> Date: Mon, 22 Nov 2010 23:22:40 +0100 Subject: [PATCH] Enable OSL_TRACE() with OSL_DEBUG_LEVEl > 0 Previously it was enabled with OSL_DEBUG_LEVEL > 1 only, while other OSL macros like OSL_ENSURE were already enabled with OSL_DEBUG_LEVEL > 0. --- sal/inc/osl/diagnose.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/sal/inc/osl/diagnose.h b/sal/inc/osl/diagnose.h index 59f921c..60f818b 100644 --- a/sal/inc/osl/diagnose.h +++ b/sal/inc/osl/diagnose.h @@ -154,7 +154,7 @@ pfunc_osl_printDetailedDebugMessage SAL_CALL osl_setDetailedDebugMessageFunc( pf #endif /* OSL_DEBUG_LEVEL */ -#if OSL_DEBUG_LEVEL > 1 +#if OSL_DEBUG_LEVEL > 0 #define _OSL_TRACE _OSL_GLOBAL osl_trace -- 1.7.3.2
Attachment:
pgpYLW8uZ5Vv9.pgp
Description: PGP signature