From: Carlo Florendo <subscribermail@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel source dependency
Date: Wed, 04 Apr 2007 09:16:07 +0800 [thread overview]
Message-ID: <4612FC57.2060207@gmail.com> (raw)
In-Reply-To: <20070403081853.6590ef84.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Tue, 03 Apr 2007 16:22:22 +0800 Carlo Florendo wrote:
>
>> Hello,
>>
>> I'm not sure whether a fix is necessary for the following scenario.
>>
>> The kernel configure target "make menuconfig" requires ncurses. FWIW, it
>> could probably be better if the error message would indicate that that
>> ncurses is necessary for "make menuconfig" to run and that the user could
>> be prompted to install the package.
>
> Hi,
> Without ncurses installed, you should see these messages:
>
> echo " *** Unable to find the ncurses libraries."
> echo " *** make menuconfig require the ncurses libraries"
> echo " *** "
> echo " *** Install ncurses (ncurses-devel) and try again"
> echo " *** "
>
> Do you not see them? or do you need something different?
Thanks. It seems I just made noise. I saw exactly the same thing you
posted, now that I've rested and it's 9:30AM. I didn't see it the other
day at 2:30AM. Maybe I need more sleep :)
Thank you very much.
Best Regards,
Carlo
--
Carlo Florendo
Softare Engineer/Network Co-Administrator
Astra Philippines Inc.
UP-Ayala Technopark, Diliman 1101, Quezon City
Philippines
http://www.astra.ph
--
The Astra Group of Companies
5-3-11 Sekido, Tama City
Tokyo 206-0011, Japan
http://www.astra.co.jp
prev parent reply other threads:[~2007-04-04 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 8:22 kernel source dependency Carlo Florendo
2007-04-03 11:50 ` Stefan Richter
2007-04-03 15:18 ` Randy Dunlap
2007-04-03 16:47 ` Jan Engelhardt
2007-04-04 1:21 ` Carlo Florendo
2007-04-04 1:16 ` Carlo Florendo [this message]
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=4612FC57.2060207@gmail.com \
--to=subscribermail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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