All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bru  <Xavier.Bru@bull.net>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [PATCH] make xconfig broken in ia64-020622
Date: Wed, 10 Jul 2002 16:06:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905757@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905745@msgid-missing>

Unfortunatly, there are more things broken with make xconfig:

. multiple conditions are not handled by tkparse:

eg: unable to set CONFIG_IA64_MCA when CONFIG_IA64_DIG is set.

if [ "$CONFIG_IA64_GENERIC" = "y" ] || [ "$CONFIG_IA64_DIG" = "y" ] \
   || [ "$CONFIG_IA64_HP_ZX1" = "y" ]; then
	bool '  Enable IA-64 Machine Check Abort' CONFIG_IA64_MCA
	define_bool CONFIG_PM y
fi

. block device options are not generated in 2.4.18:

ERROR - Attempting to write value for unconfigured variable (CONFIG_BLK_DEV_LOOP).
ERROR - Attempting to write value for unconfigured variable (CONFIG_BLK_DEV_NBD).
ERROR - Attempting to write value for unconfigured variable (CONFIG_BLK_DEV_RAM).
Having a look in tkparse.c, we can read:
" * TO DO:
 * - xconfig is at the end of its life cycle.  Contact <mec@shout.net> if
 *   you are interested in working on the replacement."

I think that the linux hackers probably use make menuconfig, as they
did not report such problems :-) ???
Xavier


  reply	other threads:[~2002-07-10 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 15:53 [Linux-ia64] [PATCH] make xconfig broken in ia64-020622 Khalid Aziz
2002-07-10 16:06 ` Xavier Bru [this message]
2002-07-10 17:05 ` Khalid Aziz
2002-07-11 21:24 ` David Mosberger
2002-07-12 20:46 ` Khalid Aziz
2002-07-19  6:54 ` Keith Owens

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=marc-linux-ia64-105590701905757@msgid-missing \
    --to=xavier.bru@bull.net \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.