Re: Linux 2.4.27-pre2 (gcc-3.4.0)

[Mikael Pettersson]

Rene Rebe writes:
 > Hi,
 > 
 > On: Wed, 5 May 2004 11:30:44 +0200,
 >     Mikael Pettersson <mikpe@xxxxxxxxx> wrote:
 > > Rafa³ 'rmrmg' Roszak writes:
 > >  > begin  Rene Rebe <rene@xxxxxxxxxxxxxxxxxxxxxxx> quote:
 > >  > 
 > >  > > It is for 2.4.26 - but should apply mostly to 2.4.27-pre2, too - I
 > >  > > have not yet booted the resulting kernel, soo ....
 > >  > 
 > >  > patching file kernel/sysctl.c
 > >  > Hunk #1 succeeded at 879 (offset 3 lines).
 > >  > Hunk #3 succeeded at 1133 (offset 3 lines).
 > >  > patching file lib/brlock.c
 > >  > patching file lib/crc32.c
 > >  > patching file lib/rwsem.c
 > >  > patching file lib/string.c
 > >  > patching file mm/filemap.c
 > >  > patching file mm/memory.c
 > >  > patching file mm/page_alloc.c
 > >  > Hunk #1 FAILED at 82.
 > >  > Hunk #2 succeeded at 241 (offset 41 lines).
 > >  > Hunk #4 succeeded at 295 (offset 41 lines).
 > >  > Hunk #6 succeeded at 486 (offset 41 lines).
 > >  > Hunk #8 succeeded at 509 (offset 41 lines).
 > >  > 1 out of 8 hunks FAILED -- saving rejects to file mm/page_alloc.c.rej
 > > 
 > > Read the archives, a solution has been available since last week. Use:
 > > http://www.csd.uu.se/~mikpe/linux/patches/2.4/patch-gcc340-fixes-2.4.27-pre2
 > > 
 > > This has been throughly tested on i386 and x86_64 UP and SMP, and ppc UP,
 > > although I have not verified drivers I don't use myself.
 > 
 > IIRC I based "my" patch uppon your's rediffed one chunk for 2.4.26 and
 > added some more driver fixes (since our build system automatically
 > enables as many as possible ...

I see. That wasn't apparent from your previous message.

Anyway, 2.4.27-pre2 changed mm/page_alloc.c in a way that caused
the gcc340 fixes patch for 2.4.27-pre1 to fail. My updated patch
for -pre2 fixes this problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/