Re: Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-07 Thread ray
did you do make oldconfig that's what I had to do to get it to work. On Sat 06 Jan at 16:26:17 -0500 [EMAIL PROTECTED] done said: > I still can't seem to get a kernel to compile under 7.0. I am using a > pristine installation, and the kernel sources etc from the install, > NOTHING ADDED/CHANGE

Re: Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-06 Thread db
> make mrproper first. I do make clean; make mrproper. Call me crazy, but for some reason I have to have make clean first. (I thought they were redundant though). ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailm

Re: Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-06 Thread Bernhard Rosenkraenzer
On Sat, 6 Jan 2001, Michael Shiels wrote: > I still can't seem to get a kernel to compile under 7.0. make mrproper LLaP bero ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list

Re: Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-06 Thread Evandro Fernandes Giovanini
Em Sábado 06 Janeiro 2001 19:26, you wrote: > I still can't seem to get a kernel to compile under 7.0. I am using a > pristine installation, and the kernel sources etc from the install, > NOTHING ADDED/CHANGED. But I get the following problem right away. > Strange thing is that it mentions the

Re: Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-06 Thread Matt Wilson
make mrproper first. Matt On Sat, Jan 06, 2001 at 04:26:17PM -0500, Michael Shiels wrote: > I still can't seem to get a kernel to compile under 7.0. I am using a > pristine installation, and the kernel sources etc from the install, > NOTHING ADDED/CHANGED. But I get the following prob

Compiling kernel under 7.0 fully updated PROBLEMS!

2001-01-06 Thread Michael Shiels
I still can't seem to get a kernel to compile under 7.0. I am using a pristine installation, and the kernel sources etc from the install, NOTHING ADDED/CHANGED. But I get the following problem right away. Strange thing is that it mentions the error as being first reference to smp_num_cpus, but