From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dominic Newton <dominic.newton@in-2-technology.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Small problem with kernel 2.6.20 and make menuconfig
Date: Tue, 13 Feb 2007 09:15:34 -0800 [thread overview]
Message-ID: <20070213091534.e4a0882e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <45D1823F.1040204@in-2-technology.co.uk>
On Tue, 13 Feb 2007 09:17:51 +0000 Dominic Newton wrote:
> Just a small issue with the latest kernel 2.6.20. When compiling make
> menuconfig our ncurses library is not being detected. I currently use
> 2.6.15 with no problem and comparing the 2 I found a script (
> scripts/kconfig/lxdialog/check-lxdialog.sh ) in the lxdialog directory
> that checks for the ncurses lib and sets compiler flags. For some reason
> it will not find the ncurses library and thus menuconfig will not
> compile and run.
>
>
>
> I have ncurses installed (and symlinked) in the usual locations (/lib,
> /usr/lib, /usr/include). I tried compiling the stock kernel in various
> locations ( /, /usr /usr/src ) - same problem every time. I fixed the
> problem by editing the scripts/kconfig/Makefile line 88-89 to ignore the
> script and set HOST_EXTRACFLAGS = -DCURSES_LOC="<ncurses.h>" and
> HOST_LOADLIBES = -lncurses.
>
> menuconfig runs perfectly now ! I'm hopeless at scripts which is why I
> gave up trying to get check-lxdialog.sh to work properly - sorry...
>
> Any queries please let me know,
What does this print? (from top of linux source tree)
$ sh scripts/kconfig/lxdialog/check-lxdialog.sh -ccflags
and
$ sh scripts/kconfig/lxdialog/check-lxdialog.sh -ldflags gcc
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-02-13 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 9:17 Dominic Newton
2007-02-13 17:15 ` Randy Dunlap [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=20070213091534.e4a0882e.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dominic.newton@in-2-technology.co.uk \
--cc=linux-kernel@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 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®