On Wed, Dec 20, 2000 at 07:34:01PM +0100, Branko Cibej wrote:
> Greg Stein wrote:
> > But yes... all that stuff can be annoying. Why don't we take it out for now.
> > I can always add it back in at some future point on a local compile.
> > Oh... Hmm. I bet that I could come up with a bit of autoconf magic to enable
> > it only on boxes that use glibc. (or at least hardcode to linux boxes at a
> > minimum)
> I'd rather see this as an extra configure flag
> (--enable-extra-warnings?) instead of making it platform-specific.
Nah. The "extra flag" is already called --with-maintainer-mode (and yes, we
should change that to --enable-maintainer-mode; we'd want to do the same
No reason to throw yet more in there. By definition, only developers are
using it, and we know how to add more flags. And as such, we can throw all
kinds of stuff in there.
> (GCC 3.0 won't emit warnings from headers found in system include
> directories (my patch, yeah!), so we /might/ want to make that default
> for --enable-maintainer-mode when it's released. But not now.)
Cool. We can certainly switch on the GCC version to add more flags. (we
already add those flags only when GCC is being used)
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:17 2006