Date: Mon, 10 Jan 2000 14:05:54 +0100 (CET) From: Alexander Leidinger <Alexander@Leidinger.net> To: bde@zeta.org.au Cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG Subject: Re: __sigisempty() undefined if "cc -g" used. Message-ID: <200001101305.OAA02110@Magelan.Leidinger.net> In-Reply-To: <Pine.BSF.4.10.10001101603040.13635-100000@alphplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Jan, Bruce Evans wrote:
>> Better yet: DEBUG_FLAGS=3D-g
>=20
> Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in
> bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included
> A few verbose module makefiles add it explicitly. You can also use
> COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel
> Makefiles.
Didn=B4t we have "makeoptions DEBUG=3D-g" as a kernel option to compile t=
he
kernel with debug information? What about "config -g MYKERNEL"?
Do we really need a global debug option which covers everything?
If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a
bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's),
right? So we only have to make the KLD's consistent to the kernel (or am
I missing something):
bsd.kmod.mk:
---snip---
92c92
< CFLAGS+=3D ${COPTS} -D_KERNEL ${CWARNFLAGS}
---
> CFLAGS+=3D ${DEBUG} -D_KERNEL ${CWARNFLAGS}
---snip---
Bye,
Alexander.
--=20
Happy new year and no Y2K-crash to everyone.
http://www.Leidinger.net Alexander+Home @ Leidinger.net
Key fingerprint =3D 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001101305.OAA02110>