I patched to pre3-8
No luck.... this really sucks :(

David Foresman wrote:
> 
> i had this same problem wih 2.3.99-pre2
> 
> patch to 2.3.99-pre3pre7
> 
> kernel.org mirror /pub/linux/kernel/testing/pre3-7.bz2 (or something like
> that)
> 
> only linux would have a pre-pre patch.
> ----- Original Message -----
> From: Robert L Martin <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 23, 2000 8:42 PM
> Subject: Re: [Cooker] Problems compiling 2.3.99-pre2
> 
> > Nitin Raja Bhatia wrote:
> >
> > > Hello,
> > >
> > > I am trying to compile 2.3.99-pre2 (with latest patches) on a Mandrake
> > > system, and I always run into problems. This really stinks.
> > >
> > > Here is the error:
> > >
> > > sysctl.c: In function `sysctl_string':
> > > sysctl.c:1135: Internal compiler error in `finish_spills', at
> > > reload1.c:3956
> > > Please submit a full bug report.
> > > See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for
> > > instructions.
> > > cpp: output pipe has been closed
> > > make[2]: *** [sysctl.o] Error 1
> > > make[2]: Leaving directory `/usr/src/linux-2.3.99-pre2/kernel'
> > > make[1]: *** [first_rule] Error 2
> > > make[1]: Leaving directory `/usr/src/linux-2.3.99-pre2/kernel'
> > > make: *** [_dir_kernel] Error 2
> > >
> > > Some info on my system:
> > > Hardware: PIII 600/256mb Ram
> > >
> >
> > just adding to the line i have a "stock" copy of 2.3.99-pre2 (direct d/l
> > from kernel.org) and it seems to choke during compiling the ipc
> > directory.
> > as far as utils i have a retail copy of L-M 7.0 with no upgrades on a P75
> > with 40 megs ram (don't laugh it takes 1.5-2 hours for it not to compile)
> >
> > side issue any help on the pppd not working? (i have a 2.3.99-pre1 kernel
> > compiled and can't surf with it)
> >
> >

-- 
     Nitin Raja Bhatia: <[EMAIL PROTECTED]>
/----------------------------------------------------\
|ICQ: 3417925  | "Where I want to go today is LINUX" |
|IRC: #Linux-Mandrake on irc.openprojects.net        |
|WEB: http://www.linuxgiant.com                      | 
\----------------------------------------------------/

Reply via email to