[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Does --enable-debug work?
From: |
Klaus Weide |
Subject: |
Re: lynx-dev Does --enable-debug work? |
Date: |
Tue, 2 Nov 1999 21:12:14 -0600 (CST) |
On Tue, 2 Nov 1999, T.E.Dickey wrote:
> > I'm not sure what that is supposed to tell me... Does it mean you
> > do not consider "--enable-debug has no effect" a bug?
>
> no - it's working as I thought it should: If you _don't_ set $CFLAGS,
> autoconf decides if gcc supports the -g option (some ports don't), and adds
> it. If you don't specify --enable-debug, I strip it out. (But I don't add
> it otherwise, since that would be ignoring the $CFLAGS value).
I would argue that --enable-debug is an explicit request to add something
to $CFLAGS (or at least to *some* variable that ends up in the command for
calling the compiler).
> > About the configure script I just want to know how to use the dang
> > thing, not how it works internally. (Well at least not now.)
>
> two choices:
> don't override $CFLAGS, and use --enable-debug.
>
> override $CFLAGS, but add -g (--enable-debug is optional)
> >
> > So what, exactly, is the "standard" way to compile lynx with debugging?
If you don't want to change the "dont't add it otherwise" -
Could you add some words to that effect to ./configure --help output
and INSTALLATION please? Something like
--enable-debug compile w/ debugging (if $CFLAGS is set, add -g
there, too)
--enable-debug (The symbol DEBUG is always defined.)
Use this option to compile-in support for debugging.
Note that this flag is ignored if the CFLAGS environment
variable is set, in that case "-g" (or whatever) has to
be included in the CFLAGS value to get debugging.
Klaus