public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Cc: kbuild-devel@lists.sourceforge.net, zippel@linux-m68k.org
Subject: Re: [PATCH]Fix menuconfig error message
Date: Mon, 4 Jul 2005 11:46:52 -0400	[thread overview]
Message-ID: <20050704154652.GA2082@kurtwerks.com> (raw)
In-Reply-To: <20050704151632.GF16867@khan.acc.umu.se>

On Mon, Jul 04, 2005 at 05:16:32PM +0200, David Weinehall wrote:
> On Mon, Jul 04, 2005 at 09:57:00AM -0400, Kurt Wall wrote:
> > 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.

[...]

> > +		echo ">> to use 'make menuconfig'. If you have an RPM-based" ;\
> > +		echo ">> Debian-based distribution you should install the" ;\ 
> > +		echo ">> ncurses-devel package." ;\
> >  		echo ;\
> >  		exit 1 ;\
> >  	fi
> 
> You know, I'd say that *very* few (approximately zero)
> Debian-based distributions are RPM-based =)  The Debian package is
> called libncurses5-dev, btw.

Silly typo. I'll post a new patch with the Debian package name.
Thanks.

Kurt
-- 
Bradley's Bromide:
	If computers get too powerful, we can organize them into a
committee -- that will do them in.

  reply	other threads:[~2005-07-04 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 13:57 [PATCH]Fix menuconfig error message Kurt Wall
2005-07-04 15:16 ` David Weinehall
2005-07-04 15:46   ` Kurt Wall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-04 15:53 Kurt Wall
2005-07-04 18:32 ` 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=20050704154652.GA2082@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