From owner-freebsd-ports Thu Dec 17 17:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20665 for freebsd-ports-outgoing; Thu, 17 Dec 1998 17:36:20 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20657 for ; Thu, 17 Dec 1998 17:36:15 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA05689 for ; Fri, 18 Dec 1998 12:06:04 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA05092; Fri, 18 Dec 1998 12:06:03 +1030 Date: Fri, 18 Dec 1998 12:06:03 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: ports@FreeBSD.ORG Subject: Canonical way to detect 3.0? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For ports which need to be patched to work on 3.0, what is the recommended compiler variable to use in patching the sourcecode (I need to #ifdef out an #include). This particular port (audio/ascd) was broken by the CAM changes, apparently (no scsi.h any more). Out of curiosity, why was this not picked up in the automated package-building which goes on? Does that machine still have a stale scsi.h in /usr/include? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message