From owner-freebsd-current Tue Oct 7 01:45:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09816 for current-outgoing; Tue, 7 Oct 1997 01:45:01 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA09802 for ; Tue, 7 Oct 1997 01:44:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id BAA00552; Tue, 7 Oct 1997 01:44:06 -0700 (PDT) Message-Id: <199710070844.BAA00552@rah.star-gate.com> To: Luigi Rizzo cc: tlambert@primenet.com, gurney_j@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: how to detect different kernel code (select or poll) In-reply-to: Your message of "Tue, 07 Oct 1997 08:13:12 BST." <199710070713.IAA07641@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Oct 1997 01:44:06 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You are lucky this time. The way I see it is patch #1 for freebsd 2.2, patch # 2 for freebsd 2.2 vs freebsd 3.0 and so on . The longer 3.0 stays in active development the harder is going to be maintaining both 2.2 and 3.0 Amancio >From The Desk Of Luigi Rizzo : > > Hi, > > > > I think that our current problem is that the poll code is not in > > 2.2 and whoever checked in the code should have at least thought of the > > incompatibility issues . One option is not to support 2.2 > > which the poll check in so far seems to imply at least with > > making things unsupported in the RELEASE is not an option in my > opinion, unless there are strong technical motivations against it, > and this is not the case. > > I browsed through the various files involved in the poll change > and could not find any way the preprocessor could tell the difference. > So I have used a new macro, USE_POLL, which must be defined in > sound.h by users who want to compile this code on 3.0. > > Fortunately it is used only in one function and one other place, so its > removal should be fine when this code finally finds its way into 2.2.X > > I am finishing the modifications and will put a new snap of the code on > my web server quite soon. > > Cheers > Luigi