From: David T Hollis <dhollis@davehollis.com>
To: linux-kernel@vger.kernel.org
Cc: Srinivas Chavva <chavvasrini@yahoo.com>
Subject: Re: Configuring kernel
Date: Sat, 14 Sep 2002 17:25:23 -0400 [thread overview]
Message-ID: <3D83A943.3010200@davehollis.com> (raw)
In-Reply-To: 02091315021800.01433@aragorn
I seem to remember either the early RH 7.x series or 6.x series did not
necessarily install ncurses by default, thus make menuconfig did not
run. If you did a very slim install, you may not have the right
libraries to do what you need. Do an 'rpm -q ncurses ncurses-devel' and
see what you get. If either is not found, make menuconfig will not run.
Adam Jaskiewicz wrote:
>>I downloaded the sofware and opened it in the /usr/src
>>directory. I did the following
>>1. unzipped the tar file
>>2. mv linux linux-2.4.16
>>3 ln -s linux-2.4.16 linux
>>4. changed to linux directory and issued the command
>>make mproper.
>>Then when I issued the command make xconfig I was
>>getting errors. I got similar errors when I tried to
>>use the following commands make menuconfig, make
>>config.
>>
>>
>
>What errors did you get? We need to know what the errors are to help you.
>
>
>
>>When I used the command uname -i I still was getting
>>the kernel version as 2.4.2.
>>I do not know why this error is coming.
>>
>>
>
>This is not an error. If you did not install a new kernel and reboot your
>computer with the new kernel, uname will still have the same kernel version.
>Once you have properly configured, compiled and installed the kernel and its
>modules, you reboot the computer to apply the new kernel. Then uname will
>give you the new version.
>
>
>
next prev parent reply other threads:[~2002-09-14 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 18:47 Configuring kernel Srinivas Chavva
2002-09-13 19:02 ` Adam Jaskiewicz
2002-09-14 21:25 ` David T Hollis [this message]
2002-09-15 22:34 ` Srinivas Chavva
2002-09-16 21:13 ` Sam Ravnborg
2002-09-16 23:19 ` Srinivas Chavva
2002-09-17 10:33 ` Paul Dickson
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=3D83A943.3010200@davehollis.com \
--to=dhollis@davehollis.com \
--cc=chavvasrini@yahoo.com \
--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