Re: make menuconfig
I re-untarred kernel-source-2.4.18-tar.bzip2 into
# /usr/src/kernel-source-2.4.18 and ran "make menuconfig"
from in there, and it worked! I *hate* reinstalling stuff
to make it work. There should be a systematic way of tracing
thru scripts as they execute, to find the cause of these
problems. When a full-screen app runs, it clears away all
the startup messages on the screen up to that point. Is
there any way to retrieve these messages?
"Joyce, Matthew" wrote:
>
> I think you need to make a symlink to that kernel folder, called linux
>
> ln -s /usr/src/kernel-source-2.4.18 /usr/src/linux
>
> Then run make menuconfig from the linux folder
>
> debpc:#/usr/src/linux/make menuconfig
>
> It works for me.
>
> "Russell" <rjshaw@iprimus.com.au> wrote in message
> news:<3D735395.8CFB4406@iprimus.com.au>...
> > Hi all,
> >
> > I'm using debian 3. When i do:
> >
> > debpc:#/usr/src/kernel-source-2.4.18# make menuconfig
> >
> > then i get a screen without any submenus. I just get:
> >
> > ---
> > Load an alternate configuration file
> > Save configuration to an alternate file
> >
> > No amount of key-pressing brings any more options.
> >
> > In scripts/Menuconfig, it says to go to
> > /usr/src/linux/scripts/lxdialog and do "make clean all". This returns:
> >
> > rm -f core *.o *~ lxdialog
> > /bin/sh: -lncurses: command not found
> > >> Unable to find the Ncurses libraries
> > >> You must have Ncurses installed in order
> > >> to use 'make menuconfig'.
> >
> > Well, ncurses 5.2 is installed. How can i test it other ways?
Reply to: