From: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>
To: zaitcev@redhat.com
Cc: linux-kernel@vger.kernel.org (kernel list),
gnb@alphalink.com.au, mec@shout.net
Subject: Re: Patch for xconfig
Date: Tue, 30 Jul 2002 14:57:30 +0200 (CEST) [thread overview]
Message-ID: <200207301257.OAA02813@green.mif.pg.gda.pl> (raw)
In-Reply-To: <200207301001.g6UA1hN14567@sunrise.pg.gda.pl> from "Andrzej Krzysztofowicz" at Jul 30, 2002 12:02:31 PM
> BTW, what I sent was a low hanged fruit that I picked.
> The main bug is worse, and I have no idea how to fix it.
> This is what we have in configuration:
>
> tristate 'ISO ...' CONFIG_ISO9660_FS
> dep_bool ' Tranparent ...' CONFIG_ZISOFS $CONFIG_ISO9660_FS
> if [ "$CONFIG_ZISOFS" = "y" ]; then
> define_tristate CONFIG_ZISOFS_FS $CONFIG_ISO9660_FS
> else
> define_tristate CONFIG_ZISOFS_FS n
> fi
>
> if [ "$CONFIG_CRAMFS" = "y" -o \
> "$CONFIG_PPP_DEFLATE" = "y" -o \
> "$CONFIG_JFFS2_FS" = "y" -o \
> "$CONFIG_ZISOFS_FS" = "y" ]; then
> define_tristate CONFIG_ZLIB_INFLATE y
> else
> if [ "$CONFIG_CRAMFS" = "m" -o \
> "$CONFIG_PPP_DEFLATE" = "m" -o \
> "$CONFIG_JFFS2_FS" = "m" -o \
> "$CONFIG_ZISOFS_FS" = "m" ]; then
> define_tristate CONFIG_ZLIB_INFLATE m
> else
> tristate 'zlib decompression support' CONFIG_ZLIB_INFLATE
> fi
> fi
IMO, the simpliest fix is to make change like replacing:
tristate 'zlib decompression support' CONFIG_ZLIB_INFLATE
with:
tristate 'zlib decompression support' CONFIG_ZLIB_INFLATE_X
define_tristate CONFIG_ZLIB_INFLATE $CONFIG_ZLIB_INFLATE_X
+ rename the option in a help file (if it exist)
(not tested, but should work)
> As far as I can tell, tkgen.c does an acceptable job on the
> second part; though it refuses to generate "else" and uses
> de Morgan transformation instead. However, it seems that tkparse
> chokes on the very innocently looking first part. The result
> is that xconfig insist on zlib to be a module when it should
> be compiled into the kernel; it all ends with undefined symbols.
> Naturally, "make oldconfig" works correctly.
No. The problem is that variales associated with eg. "tristate" clauses
are always modified (even if its condition is false) during configuration
refreshment - to store the previous value for the option.
Not good, but it is just bad project. Nobody wanted to rewrite xconfig
as CML2 was assumed to come soon...
> The code in the menu part of kconfig.tk fixes the problem.
> In other words, the bug is only visible if someone does "make xconfig",
> loads a canned configuration which we ship, then does "save
> and exit" immediately. If he visits any menus, everything is ok.
I'm not sure it is so simple...
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Gdansk University of Technology
next parent reply other threads:[~2002-07-30 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207301001.g6UA1hN14567@sunrise.pg.gda.pl>
2002-07-30 12:57 ` Andrzej Krzysztofowicz [this message]
2002-07-28 12:40 Greg Banks
2002-07-29 23:15 ` Pete Zaitcev
2002-07-31 14:59 ` Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2002-07-27 2:43 Pete Zaitcev
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=200207301257.OAA02813@green.mif.pg.gda.pl \
--to=ankry@green.mif.pg.gda.pl \
--cc=gnb@alphalink.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®