public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Patrick Finnegan <pat@purdueriots.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig (qt) -> Gconfig (gtk)
Date: Sat, 2 Nov 2002 22:06:58 +0000	[thread overview]
Message-ID: <20021102220658.C8549@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211021652470.16432-100000@ibm-ps850.purdueriots.com>; from pat@purdueriots.com on Sat, Nov 02, 2002 at 04:57:31PM -0500

On Sat, Nov 02, 2002 at 04:57:31PM -0500, Patrick Finnegan wrote:
> Personally, it makes no difference to me which library is used.  I'm
> doubtful I'll use anything other than menuconfig unless it makes my life a
> *whole* lot easier. I'd say 'choose one and get on with it.'

Looking at my menuconfig patch (that's been mailed to lkml numerious
times), the old Menuconfig script and checking mconf.c, it looks like
mconf.c isn't checking for half the errors that the old Menuconfig
script used to / would've been checking with my patch.

Oh, and another thing I've noticed is that mconf does nothing if it
fails to execute lxdialog - it doesn't tell you _why_ it's doing
nothing.  It just says something like "Not saving configuration."

The last mailing of my patch was a while ago, so I'll reproduce it
here:

| This patch fixes a failure case in menuconfig which can occur if a kernel
| tree is configured on one architecture with menuconfig, and then attempted
| to be reconfigured on another architecture.
| 
| The kernel detects that the binary can't be run on the second architecture
| and correctly returns the appropriate error code.  However, the Menuconfig
| script ignores this error and retries endlessly, appearing to hang.
| 
| This patch makes menuconfig display a message and exit rather than
| endlessly looping.
| 
|  scripts/Menuconfig |   20 ++++++++++++++++++++
|  1 files changed, 20 insertions
| 
| diff -ur orig/scripts/Menuconfig linux/scripts/Menuconfig
| --- orig/scripts/Menuconfig	Sat Oct 12 10:02:17 2002
| +++ linux/scripts/Menuconfig	Sat Oct 12 10:45:13 2002
| @@ -909,6 +909,26 @@
|  			cleanup
|  			exit 139
|  			;;
| +		126|127)
| +			stty sane
| +			clear
| +			cat << EOM
| +
| +There seems to be a problem with the lxdialog companion utility which is
| +built prior to running Menuconfig.  lxdialog could not be found, or could
| +not be executed.  This can be caused when lxdialog has been built for a
| +different architecture.
| +
| +You should rebuild lxdialog.  This can be done by moving to the
| +/usr/src/linux/scripts/lxdialog directory and issuing the "make clean all"
| +command.
| +
| +If the problem persists, you may email the maintainer <mec@shout.net> or
| +post a message to <linux-kernel@vger.kernel.org> for additional assistance. 
| +
| +EOM
| +			cleanup
| +			exit 1
|  		esac
|  	done
|  }
| 

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-11-02 22:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 22:21 Kconfig (qt) -> Gconfig (gtk) Romain Lievin
2002-11-02  7:03 ` Nero
2002-11-02 20:36   ` Dr. David Alan Gilbert
2002-11-02 17:00     ` Jon Portnoy
2002-11-02 22:19       ` bert hubert
2002-11-02 19:45     ` Nero
2002-11-02 20:42     ` Xavier Bestel
2002-11-02 21:12       ` David B. Stevens
2002-11-02 21:07     ` Russell King
2002-11-02 22:43       ` Marek Habersack
2002-11-02 22:48         ` Sam Ravnborg
2002-11-02 21:25     ` Dave Jones
2002-11-02 21:59     ` Alan Cox
2002-11-02 21:57       ` Patrick Finnegan
2002-11-02 22:06         ` Russell King [this message]
2002-11-02 22:33           ` Roman Zippel
2002-11-02 22:34             ` Russell King
2002-11-03  3:18               ` Gerhard Mack
2002-11-02 22:47             ` Sam Ravnborg
2002-11-02 23:03               ` Roman Zippel
2002-11-02 22:56         ` Alan Cox
2002-11-02 23:07           ` Patrick Finnegan
2002-11-03  4:07           ` Matthew D. Pitts
2002-11-04  4:57           ` Stefan Traby
2002-11-04  6:21             ` Sam Ravnborg
2002-11-02 23:28         ` Dr. David Alan Gilbert
2002-11-02 22:43           ` Nero
2002-11-02 23:59             ` Roman Zippel
2002-11-03  0:06               ` J.A. Magallón
2002-11-02 23:16                 ` Nero
2002-11-03  1:30                 ` Alan Cox
2002-11-03  3:09                   ` Christoph Hellwig
2002-11-03  9:47                     ` Geert Uytterhoeven
2002-11-03 12:56                       ` Christoph Hellwig
2002-11-03  4:42                   ` Randy.Dunlap
2002-11-03  0:07             ` Patrick Finnegan
2002-11-03  3:53             ` George Staikos
2002-11-03  9:08               ` Nero
2002-11-06  0:45         ` Bill Davidsen
2002-11-06  1:25           ` Mariusz Zielinski
2002-11-03  1:15     ` Rando Christensen
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 13:43 Where's the documentation for Kconfig? Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel
2002-11-01 12:52   ` Russell King
2002-11-01 13:50     ` Roman Zippel
2002-11-01 19:31       ` Russell King
2002-11-01 20:35         ` Roman Zippel
     [not found]           ` <20020625221306.GA439@free.fr>
     [not found]             ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20               ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45                 ` Roman Zippel

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=20021102220658.C8549@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pat@purdueriots.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