Re: gnome-libs and --disable-debug in the configure script

FYI this was fixed yesterday in CVS.


On 25 Jan 1999, Robert Bihlmeyer wrote:

> Hi,
> >>>>> On Sun, 24 Jan 1999 23:56:43 -0500 (EST)
> >>>>> Gleef <> said:
>  Gleef> On Sun, 24 Jan 1999, Damo wrote:
>  >> the subject is pretty much most of my message. when i do
>  >> ./configure --disable-debug (or --disable-debug to be
>  >> pedantic), instead of less debug messages (i dont think i got any
>  >> before), i get more! all this stuff about various things clicked
>  >> and activates. basically a much more verbose debug output.
> FYI: debugging is off by default, you won't get less debug messages by 
> turning it off a second time. I'd guess that those messages you're
> seeing come from gtk+, not gnome-libs.
>  Gleef> That's one of the more annoying quirks of autoconf. Unless you
>  Gleef> go through a lot of effort setting up the script,
>  Gleef> autoconf will recognize both --enable-<feature> and
>  Gleef> --disable-<feature> as both doing the same thing, toggling
>  Gleef> <feature> from the default behavior. It leaves it up to the
>  Gleef> configure script writer to set a default and list the correct
>  Gleef> form of the option, and up to the person running configure to
>  Gleef> follow directions :-).
> Well, normally you just set another variable to $enableval. For
> --enable-debug, the following mini-patch should help:

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]