[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev [PATCH][dev22] Fix --disable-trace, #includes
From: |
John Bley |
Subject: |
Re: lynx-dev [PATCH][dev22] Fix --disable-trace, #includes |
Date: |
Sat, 17 Apr 1999 08:58:06 -0400 (EDT) |
On Sat, 17 Apr 1999, Klaus Weide wrote:
> > * Fix --disable-trace, chop more unneeded #includes (John Bley)
> Could you explain why --disable-trace needed fixing? It seems to
> me you change doesn't really change anything - you now just test
> for NO_LYNX_TRACE directly rather than indirectly (through DEBUG),
> or am I missing something?
Yes, that's what I thought too, but for some reason
./configure --disable-trace && make all
was still producing a binary that could do tracing. (I.e., produces
Lynx.trace and fills it with junk). I tried with both gcc and Sun's cc.
I don't claim to fully understand why this particular fix works for me,
but now when I disable-trace I really don't produce the trace.
> > Strange:
> > Turning trace off at compile-time transforms all instances of
> > CTRACE(...)
> > to
> > if (0) fprintf(...)
>
> Are you really compiling with -O[>=2] and without -g?
For gcc, yes. Also the appropriate flags for cc. It is quite strange.
--
John Bley - address@hidden
Duke '99 - English/Computer Science
Since English is a mess, it maps well onto the problem space,
which is also a mess, which we call reality. - Larry Wall