From: Keith Owens <kaos@ocs.com.au>
To: DaZZa <dazza@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems compiling kernel greater than 2.4.7
Date: Tue, 12 Mar 2002 14:09:18 +1100 [thread overview]
Message-ID: <6807.1015902558@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 12 Mar 2002 13:35:15 +1100." <Pine.LNX.4.30.0203121326420.12771-100000@zipperii.zip.com.au>
On Tue, 12 Mar 2002 13:35:15 +1100 (EST),
DaZZa <dazza@zip.com.au> wrote:
>I'm attempting to compile a new kernel. 2.4.14 by preference, but this
>problem also exists with every version I've tried beyond 2.4.7.
>
>On installing a clean copy of the kernel source tree for ANY version after
>2.4.7, I perform the following
>
>cd /usr/src
>ln -s linux-2.4.14 linux
>cd linux
>make mrproper
>make menuconfig
>
>At this point, menuconfig runs, and I receive the initial, "Linux 2.4.14
>Kernel Configuration" blue yellow and white screen.
>
>However, selecting *ANY* menu option at this point gives the following
>error message
>
>===cut===
>There seems to be a problem with the lxdialog companion utility which is
>built prior to running Menuconfig. Usually this is an indicator that you
>have upgraded/downgraded your ncurses libraries and did not remove the
>old ncurses header file(s) in /usr/include or /usr/include/ncurses.
An alternative cause is an incorrectly coded menu option. Try make
xconfig, the xconfig code is much more rigorous about checking for
incorrect CML1 syntax.
next prev parent reply other threads:[~2002-03-12 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 2:35 Problems compiling kernel greater than 2.4.7 DaZZa
2002-03-12 3:09 ` Keith Owens [this message]
2002-03-12 7:03 ` DaZZa
2002-03-13 16:52 ` Hans-Peter Jansen
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=6807.1015902558@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=dazza@zip.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.