do make mrproper BUT before you do copy your config file i think it is ( sorry
in windows right now can't check ) somewhere else so not overwritten...then copy
it back and start again..
hth's
lee
Andy Worthington wrote:
I am having trouble compiling a new kernel. This is a fresh install of
OK people - how many times do we have to say this:
SEARCH THE ARCHIVES!!
This question has been answered (literally) hundreds of times by now.
Andy: Use kgcc instead of gcc is the official answer. Unofficially i think
if you do a "make distclean" then everything should work.
ubject: RE: kernel compile problems
OK people - how many times do we have to say this:
SEARCH THE ARCHIVES!!
This question has been answered (literally) hundreds of times by now.
Andy: Use kgcc instead of gcc is the official answer. Unofficially i
think
if you do a "make distclean&q
I'm having the same problem. I changed the CC definition to use kgcc
(which is installed), even though mine had some logic that should have
resulted in the same thing anyway, and it made no difference.
What else can I check?
kernelcfg-0.6-9
kernel-headers-2.4.0-0.26
kernel-2.2.16-22
shortly after I sent this, I tried a make mrproper oldconfig dep and then
it magically worked. The mrproper seems to have done it, since I checked
another 7.0 box (upgraded not clean install) with the same problem, and it
fixed it there too - without changing the Makefile.
I guess the list
gcc is your standard issue C compiler. Have you ever compiled a kernel
from tarball?
On Thu, 28 Sep 2000, Mr FW User wrote:
You should be using cc or gcc to compile anything on
a redhat system... including the kernel.
Well, apparently this kgcc is specifically designed to
compile the
On Thu, Sep 28, 2000 at 11:57:24PM -0400, Statux wrote:
: gcc is your standard issue C compiler. Have you ever compiled a kernel
: from tarball?
What he's saying here is that the stock gcc in 7.0 blows up on compiling
kernel 2.2.x, as it is gcc 2.96. This same problem existed with the 2.0
On Thu, 28 Sep 2000, Mr FW User wrote:
Hi. I've just installed 7.0 on a blank disk and now
understand there is a 'kgcc' that must be used to
compile the kernel. I removed gcc and linked kgcc to
I have a question. Where did 'kgcc' come from? The
core kernel development group, or did it come
What's going on? The kernel compiles okay, but this
doesn't give me the warm-and-fuzzy... Why does this
seem so half-assed?
You should be using cc or gcc to compile anything on a redhat
system... including the kernel.
___
Redhat-list mailing list
On Thu, Sep 28, 2000 at 06:45:25PM -0700, Mr FW User wrote:
: Hi. I've just installed 7.0 on a blank disk and now
: understand there is a 'kgcc' that must be used to
: compile the kernel. I removed gcc and linked kgcc to
: gcc and cc in /usr/bin. Now, I'm receiving the
: following assembly
Warnings aren't really anything to be all that worried about. If you have a
kernel, just be happy :o)
--MB
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mr FW User
Sent: Thursday, September 28, 2000 9:45 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
You should be using cc or gcc to compile anything on
a redhat system... including the kernel.
Well, apparently this kgcc is specifically designed to
compile the kernel, due to it being a new version, I
think?
So you're able to compile the kernel using:
cpp-2.96-54
kernel-2.2.16-22
12 matches
Mail list logo
