Re: 2.4.18-pre9-mjc2 compile errors

[Michael Cohen <me@ohdarn.net>]

On Mon, 2002-02-18 at 16:50, Bill Davidsen wrote:
> On 18 Feb 2002, Michael Cohen wrote:
> 
> > On Mon, 2002-02-18 at 13:25, root@deathstar.prodigy.com wrote:
> > > filemap.c: In function `__find_page_nolock':
> > > filemap.c:404: structure has no member named `next_hash'
> > > make[2]: *** [filemap.o] Error 1
> > > make[2]: Leaving directory `/usr/src/linux/mm'
> > > make[1]: *** [first_rule] Error 2
> > > make[1]: Leaving directory `/usr/src/linux/mm'
> > > make: *** [_dir_mm] Error 2
> > 
> > There was a fix posted to lkml earlier, though I'd say that likely if
> > you can't fix this, you don't need to run this kernel. try looking at
> > lkml.  Next version will have it fixed, however. =)
> 
> I didn't ask for a fix, I was offering a problem report, from a machine
> with no lkml or anything else (don't let the name and IP fool you, I was
> testing). I was trying to add it to my summary of recent kernels which run
> well on small slow machines which might be available for the asking.
> 
> I included the config because I thought the P5 might be triggering a
> problem others hadn't tested, but it looks as if everyone had the problem.
> I thought these were like -ac patches which has already been tested to see
> if they compile.
Sorry, I wasn't in too great of a mood.  Didn't mean to sound *that*
rough.  Anyways, I had just started using bitkeeper, and the change
didn't get committed properly, so it fell out of my bk tree when I made
the patch.  It had been tested mostly though.  I started using a much
more inclusive test .config though; and I'll have a working next
release.  Take a look at how well 2.5 currently compiles though =)

Fix is to remove the function __find_page_nolock from mm/filemap.c.

------
Michael Cohen
OhDarn.net