From: Giacomo Catenazzi <cate@debian.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 15:32:08 +0100 [thread overview]
Message-ID: <3C7504E8.3000604@debian.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0202211456380.2650-100000@serv>
Roman Zippel wrote:
> Hi,
>
> On Thu, 21 Feb 2002, Giacomo Catenazzi wrote:
>
>
>>1) default: Eric proposed to include defaults in configuration,
>> but it seems that is a bad things, and defaults should be arch
>> specific. (I don't remember the discussion, but you can
>> parse the kbuild list, torque.net time)
>>
>
> The defaults are just 1:1 representation of the current define_xxx
> statements. These can be of course later moved or depreciated or whatever.
Ok. But actually the defaults come mainly from config.def.
The define_xxx are uset to set a symbols in some situations.
BTW for people who like the old configure (or fix it):
: if xxx
: define_bool CONFIG_FOO
: else
: bool CONFIG_FOO
: fi
is incorrect. You should revert the definition order
(before bool than define_bool) else xconfig will break.
>>2) One of the problem in actual configure are the dependencies.
>> FOO depend on BAR and BEER.
>> Wat are the possible value of FOO if BAR=m, BEER=y.
>> In kernel we have some drivers thet need foo to be n or y,
>> in other cases: n or m.
>> The logical operators hide the true dependency table.
>> (don't expect developers read the docs: the logical operators
>> seems like C operators, so they use like C, but they forget
>> the third case (=m) ).
>>
>
> For most cases I've seen it can be very simply defined with:
> (a && b && ...) = min(a, b, ...)
> (a || b || ...) = max(a, b, ...)
> for 'n'=0, 'm'=1, 'y'=2
With this you have a value (i.e. n,m,y).
How is the actual symbol range?
CONFIG_FOO:
dep: (FREE? && BEER?)
how you tell configuration rools that
FOO can be only min/max of (FREE? && BEER?)
> Do you have some real examples?
No by hand. But I can search in rules.
>>Do you use the python identation mode?
>>
>
> No python. Just c, flex and bison. :-)
I mean: Do you use pythons mode to tell when a
help description end (no tab: new symbol), few spaces:
is symbol help or configuration symbols)
giacomo
next prev parent reply other threads:[~2002-02-21 14:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` linux kernel config converter Giacomo Catenazzi
2002-02-21 14:11 ` Roman Zippel
2002-02-21 14:32 ` Giacomo Catenazzi [this message]
2002-02-21 15:19 ` Roman Zippel
[not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
[not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06 ` Giacomo Catenazzi
2002-02-21 14:26 ` Jeff Garzik
2002-02-21 14:39 ` Giacomo Catenazzi
2002-02-21 15:11 ` Jeff Garzik
2002-02-21 16:00 ` Randy.Dunlap
[not found] ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50 ` Giacomo Catenazzi
2002-02-21 14:56 ` David Lang
2002-02-21 15:05 ` Giacomo Catenazzi
2002-02-21 10:48 Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21 ` Roman Zippel
2002-02-21 12:32 ` Jeff Garzik
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21 ` Jeff Garzik
2002-02-21 14:28 ` David Lang
2002-02-21 14:36 ` Jeff Garzik
2002-02-21 14:40 ` David Lang
2002-02-21 15:05 ` Jeff Garzik
2002-02-21 15:41 ` Jason Lunz
2002-02-21 15:54 ` Jeff Garzik
2002-02-21 15:18 ` Alan Cox
2002-02-21 15:08 ` Jeff Garzik
2002-02-21 15:22 ` Gerd Knorr
2002-02-21 15:33 ` Roman Zippel
2002-02-21 18:53 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7504E8.3000604@debian.org \
--to=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox