Date: Wed, 18 Aug 2004 09:27:09 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John-Mark Gurney <jmg@FreeBSD.org> Cc: current@FreeBSD.org Subject: kqueue is safe to use? Message-ID: <20040818062709.GC6348@ip.net.ua> In-Reply-To: <20040818045206.GD99980@funkthat.com> References: <200408172029.35506.mjohnston@skyweb.ca> <20040818045206.GD99980@funkthat.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Tue, Aug 17, 2004 at 09:52:06PM -0700, John-Mark Gurney wrote:
> Mark Johnston wrote this message on Tue, Aug 17, 2004 at 20:29 -0500:
> > Here's this week's giant summary. As you probably know, a code freeze went
> > into effect first thing on the 17th, which is the main reason for the length
> > of this summary.
>
> Another change you forgot is that I commit patches to make kqueue safe
> to use on -current. This has been a long outstanding problem with
> -current.
>
Would the following be safe to commit now?
%%%
Index: Makefile
===================================================================
RCS file: /home/ncvs/src/usr.bin/make/Makefile,v
retrieving revision 1.33
diff -u -r1.33 Makefile
--- Makefile 12 Aug 2004 11:49:55 -0000 1.33
+++ Makefile 18 Aug 2004 06:23:06 -0000
@@ -18,11 +18,10 @@
CFLAGS+=-DMAKE_VERSION=\"5200408120\"
.if defined(_UPGRADING)
CFLAGS+=-D__FBSDID=__RCSID
+.else
+CFLAGS+=-DUSE_KQUEUE
.endif
-# XXX: kernel currently broken
-# CFLAGS+=-DUSE_KQUEUE
-
main.o: ${MAKEFILE}
# Set the shell which make(1) uses. Bourne is the default, but a decent
%%%
Cheers,
--
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)
iD8DBQFBIva9qRfpzJluFF4RAk5TAJ0eA2xjXOMPleXN3+nxIk+gIPstNwCfZweL
2GkuCelLRo4Pfb5J3DIXAt4=
=pK2N
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040818062709.GC6348>