From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
kbuild-devel@lists.sourceforge.net
Subject: [PATCH]Fix menuconfig error message
Date: Mon, 4 Jul 2005 11:53:50 -0400 [thread overview]
Message-ID: <20050704155350.GB2082@kurtwerks.com> (raw)
If you try to run `make menuconfig' on a system that lacks ncurses
development libs, you get an error message telling you to install
ncurses-devel. Some popular distributions don't have an ncurses-devel
package. This patch generalizes the error message. Patch is against
2.6.12.
This patch fixes a silly typo conflating RPM-based systems with Debian
derivatives and adds the name of the Debian package to install.
MAINTAINERS doesn't list a maintainer for menuconfig or lxdialog,
so I sent this to lkml, kbuild-devel, and to the kconfig maintainer.
Signed-off-by: Kurt Wall <kwall@kurtwerks.com>
--- a/scripts/lxdialog/Makefile 2005-07-04 09:54:44.000000000 -0400
+++ b/scripts/lxdialog/Makefile 2005-07-04 11:50:00.000000000 -0400
@@ -35,8 +35,11 @@
echo -e "\007" ;\
echo ">> Unable to find the Ncurses libraries." ;\
echo ">>" ;\
- echo ">> You must install ncurses-devel in order" ;\
- echo ">> to use 'make menuconfig'" ;\
+ echo ">> You must install ncurses development libraries" ;\
+ echo ">> to use 'make menuconfig'. If you have an RPM-based" ;\
+ echo ">> distribution you should install the ncurses-devel" ;\
+ echo ">> Debian users will probably want to install the
+ echo ">> libncurses5-dev package." ;\
echo ;\
exit 1 ;\
fi
--
Rule of Feline Frustration:
When your cat has fallen asleep on your lap and looks utterly
content and adorable, you will suddenly have to go to the bathroom.
next reply other threads:[~2005-07-04 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 15:53 Kurt Wall [this message]
2005-07-04 18:32 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2005-07-04 13:57 Kurt Wall
2005-07-04 15:16 ` David Weinehall
2005-07-04 15:46 ` Kurt Wall
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=20050704155350.GB2082@kurtwerks.com \
--to=kwall@kurtwerks.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®