linux-kernel - Re: menuconfig issue (checklist) in 2.6.20.7 & 2.6.21-rc7 ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070425203009.GA15917@uranus.ravnborg.org>
Date:	Wed, 25 Apr 2007 22:30:09 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Mike Galbraith <efault@....de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Sunil Naidu <akula2.shark@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: menuconfig issue (checklist) in 2.6.20.7 & 2.6.21-rc7 ?

> > > [sukhoi@...la2 linux-2.6.20.7]$ sudo make menuconfig
> > >   HOSTCC  scripts/kconfig/lxdialog/checklist.o
> > > In file included from scripts/kconfig/lxdialog/checklist.c:24:
> > > scripts/kconfig/lxdialog/dialog.h:32:20: error: curses.h: No such file
> > > or directory
> > 
> > I guess you need to install the curses development package.  Here it's called
> > ncurses-devel.
check-lxdialog.sh should be extended to catch this case.
We can link but .h file is not present.
Will take a look at it later.

> There are general funnies in the menuconfig world (my preference) here.
> For instance, I recently had reason to change/test different default IO
> schedulers, and found that no matter what I did, I couldn't select a
> default IO scheduler any more, though I used to be able to do so.
Tried it now with latest -git from Linus and here it works.
Notice that you need to make the scheduler a built-in <*>
before you can select it as default.
A scheduler selected as a module <M> cannot be made default.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/