From owner-freebsd-current Thu Oct 1 10:51:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29486 for freebsd-current-outgoing; Thu, 1 Oct 1998 10:51:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29473 for ; Thu, 1 Oct 1998 10:51:46 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA02773; Thu, 1 Oct 1998 19:54:05 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 1 Oct 1998 19:54:04 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Eivind Eklund cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: "options" for -current ... In-Reply-To: <19981001163548.48870@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Oct 1998, Eivind Eklund wrote: > On Thu, Oct 01, 1998 at 01:15:25PM +0100, Luigi Rizzo wrote: > > Do i get it right that "config" in -current is different from -stable > > in handling "options XYZ" statements ? > > > > Under -stable, "options XYZ" would bring in files listed in conf/files > > as > > > > filename optional xyz > > > > wherease in -current it seems not (i.e. i have to add an entry in > > conf/options for that ?) > > I don't think there should be any difference in _that_, but you should > _always_ add an entry to conf/options (or a machine-specific variant) > if you add new options. You should also add the option to LINT. I beg to differ: in -current (as it seems) you should add your option to /sys/conf/options, which will create appropriate "opt_something.h" file which you should in turn include in your module to see if the code is needed. If you don't do this, you're harshly rebuked by 'config' each time, and the option is used as a global -D define, which can conflict with some #defines in other modules. In -stable this wasn't enforced, and the "options" were being translated just to global -D defines. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message