Date: Thu, 5 Feb 1998 20:54:38 +1100 From: Bruce Evans <bde@zeta.org.au> To: eivind@yes.no, wollman@khavrinen.lcs.mit.edu Cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf options src/sys/gnu/ext2fs ext2_alloc.c ext2_balloc.c ext2_inode.c ext2_lookup.c ext2_subr.c ext2_vnops.c src/sys/i386/i386 busdma_machdep.c machdep.c pmap.c swtch.s trap.c vm86.c vm_machdep.c src/sys/i386/ibcs2 ibcs2_sysi86. Message-ID: <199802050954.UAA31717@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>>[DIAGNOSTIC] >Well, the way I've always used it was to turn it on for just those >specific modules I was debugging. That keeps the code perturbation That should still work, since if DIAGNOSTIC is not configured, then opt_diagnostic.h will not define DIAGNOSTIC, so you can still use `make COPTFLAGS=-DDIAGNOSTIC'. `make COPTFLAGS=-DDIAGNOSTIC=0' won't work to turn off DIAGNOSTIC if it is configured, but it is already broken, since COPTFLAGS and COPTS are almost perfectly misplaced at the beginning and near the end of CFLAGS respectively, so COPTFLAGS can't be used to override COPTS. Similarly for DEBUG. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802050954.UAA31717>