[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to menuconfig 2.0.35 & ncurses?



On Thu, Dec 10, 1998 at 09:48:43PM -0500, Avery Pennarun wrote:
> On Thu, Dec 10, 1998 at 04:59:13PM -0800, Oscar Levi wrote:
> 
> > I getting errors from 
> > 
> >   make menuconfig
> > 
> > in the Linux kernel 2.0.35 source tree.  It says that my ncurses
> > headers are incorrect.  I replaced ncurses3.4-dev with
> > libncurses4-dev and I get the same problem.  Kernel 2.1.131 works
> > fine.  Is there a trick to this?
> 
> You'll never get any good answer to a problem like this unless you give us
> the compiler output.

Fair enough.

   rm -f include/asm
   ( cd include ; ln -sf asm-i386 asm)
   make -C scripts/lxdialog all
   make[1]: Entering directory `/m/md0/src/linux/scripts/lxdialog'
   make[1]: Leaving directory `/m/md0/src/linux/scripts/lxdialog'
   /bin/sh scripts/Menuconfig arch/i386/config.in

   Using defaults found in .config
   scripts/Menuconfig: line 1183:  1869 Segmentation fault      $DIALOG --backtitle "$backtitle" --infobox "Preparing configuration scripts..." 3 40
   
   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.

   It is VERY important that you have only one set of ncurses header files
   and that those files are properly version matched to the ncurses libraries 
   installed on your machine.

   You may also need to rebuild lxdialog.  This can be done by moving to
   the /usr/src/linux/scripts/lxdialog directory and issuing the 
   "make clean all" command.

   If you have verified that your ncurses install is correct, you may email
   the author <roadcapw@titus.org> or post a message on the linux.dev.kernel
   news group for additional assistance. 

   make: *** [menuconfig] Error 139

I would guess that the error is bogus since the newer kernel builds
OK.  I suspect that this is one of those boneheaded problems that someone else says, "Just turn the red switch to ON and it'll work."


Reply to: