From: Roger While <simrw@sim-basis.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: menuconfig bust in 2.6.19rc1-git5
Date: Mon, 09 Oct 2006 13:03:07 +0200 [thread overview]
Message-ID: <6.1.1.1.2.20061009125614.02a6e000@192.168.6.12> (raw)
In-Reply-To: <20061009094609.GA6703@uranus.ravnborg.org>
Aaagh, sorry, false alarm.
There was a dud (0 byte) /usr/include/ncurses/ncurses.h on the system :-(
(However /usr/include/ncurses.h is perfectly OK)
Maybe check-lxdialog.sh should 'test -s' the includes ?
Roger
>On Mon, Oct 09, 2006 at 09:30:06AM +0200, Roger While wrote:
> > > make menuconfig
> > HOSTCC scripts/basic/fixdep
> > HOSTCC scripts/basic/docproc
> > HOSTCC scripts/kconfig/conf.o
> > HOSTCC scripts/kconfig/kxgettext.o
> > HOSTCC scripts/kconfig/lxdialog/checklist.o
> > In file included from scripts/kconfig/lxdialog/checklist.c:24:
> > scripts/kconfig/lxdialog/dialog.h:96: error: syntax error before "chtype"
> > scripts/kconfig/lxdialog/dialog.h:96: warning: no semicolon at end of
> > struct or union
>
>This looks like some type is missing.
>I do not expect to be within reach of my linux box the next week - du you have
>the possibility to try a few thing to sort it out?
>
>Take a look at line 96 (and one or two lines before) and check what type
>is used there. Then try to find out in which header file
>it is supposed to be defined and include this header file in dialog.h.
>
>This should keep you going again.
>
>It may also be that you need to install a later version of ncurses to get
>it operational.
>
> Sam
next prev parent reply other threads:[~2006-10-09 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 7:30 Roger While
2006-10-09 9:46 ` Sam Ravnborg
2006-10-09 11:03 ` Roger While [this message]
2006-10-09 19:27 ` Sam Ravnborg
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=6.1.1.1.2.20061009125614.02a6e000@192.168.6.12 \
--to=simrw@sim-basis.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®