From: Keith Owens <kaos@ocs.com.au>
To: John Peel <jrp@thepeel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make menuconfig fails
Date: Sat, 02 Mar 2002 12:21:25 +1100 [thread overview]
Message-ID: <2009.1015032085@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 01 Mar 2002 11:26:02 MDT." <Pine.LNX.4.33.0203011118460.3337-100000@thepeel.org>
On Fri, 1 Mar 2002 11:26:02 -0600 (CST),
John Peel <jrp@thepeel.org> wrote:
>I just setup a new box running RH7.2 and I am trying to compile kernel
>2.4.18. I did a minimal install on this box as it is only going to function as a router. When I
>initially did a 'make menuconfig' it gave me an error regarding ncurses
>being missing. I installed ncurses, ncurses4, and ncurses-devel. Now when
>I do a 'make menuconfig' I get the following output:
>
>[root@localhost linux]# make menuconfig
>rm -f include/asm
>( cd include ; ln -sf asm-i386 asm)
>make -C scripts/lxdialog all
>make[1]: Entering directory `/usr/src/linux/scripts/lxdialog'
>gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DLOCALE
>-I/usr/include/ncurses -DCURSES_LOC="<ncurses.h>" -c -o checklist.o
>checklist.c
>checklist.c: In function `dialog_checklist':
>checklist.c:154: `TRUE' undeclared (first use in this function)
TRUE should be defined in /usr/include/ncurses/ncurses.h, like this
/* XSI and SVr4 specify that curses implements 'bool'. However, C++ may also
* implement it. If so, we must use the C++ compiler's type to avoid conflict
* with other interfaces.
*/
#undef TRUE
#define TRUE 1
#undef FALSE
#define FALSE 0
next prev parent reply other threads:[~2002-03-02 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 17:26 John Peel
2002-03-01 18:33 ` Thang T. Mai
2002-03-01 20:13 ` John Peel
2002-03-02 1:21 ` Keith Owens [this message]
2002-03-02 16:54 ` John Peel
2004-04-05 7:01 Make " Richard Harke
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=2009.1015032085@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=jrp@thepeel.org \
--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®