mm-sources + fbsplash patch breaks kernel compile (solved)

[Inhale]

Trying out Spock's fbsplash+vesa-2.6.12-mm1.patch against the correct kernel (symlink is linux -> linux-2.6.12-mm1)

Patch applies correctly without errors, however:

wnswsexc linux # make
CHK include/linux/version.h
scripts/kconfig/conf -s arch/i386/Kconfig
#
# using defaults found in .config
#
SPLIT include/linux/autoconf.h -> include/config/*
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
CHK usr/initramfs_list
GZIP kernel/config_data.gz
IKCFG kernel/config_data.h
CC kernel/configs.o
LD kernel/built-in.o
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
fs/built-in.o(.text+0x925d2): In function `gzip1_alloc':
: undefined reference to `zlib_deflate_workspacesize'
fs/built-in.o(.text+0x925e3): In function `gzip1_alloc':
: undefined reference to `zlib_deflate_workspacesize'
fs/built-in.o(.text+0x92722): In function `gzip1_compress':
: undefined reference to `zlib_deflateInit2_'
fs/built-in.o(.text+0x92735): In function `gzip1_compress':
: undefined reference to `zlib_deflateReset'
fs/built-in.o(.text+0x92764): In function `gzip1_compress':
: undefined reference to `zlib_deflate'
drivers/built-in.o(.init.text+0x29d5): In function `vesafb_vbe_init':
: undefined reference to `fb_get_monitor_limits'
drivers/built-in.o(.init.text+0x2a04): In function `vesafb_vbe_init':
: undefined reference to `fb_create_modedb'
make: *** [.tmp_vmlinux1] Error 1


Any pointers as to how to proceed?

[Inhale]

fixed - found a new patch at http://lkml.org/lkml/2005/6/20/231

> >--- 2.6.12-mm1/fs/reiser4/Kconfig 2005-06-20 07:38:22.087653000 -0400
> >+++ linux/fs/reiser4/Kconfig 2005-06-20 08:01:28.914324250 -0400
> >@@ -1,6 +1,8 @@
> > config REISER4_FS
> > tristate "Reiser4 (EXPERIMENTAL)"
> >- depends on EXPERIMENTAL && !4KSTACKS && ZLIB_INFLATE
> >+ depends on EXPERIMENTAL && !4KSTACKS
> >+ select ZLIB_INFLATE
> >+ select ZLIB_DEFLATE
> > help
> > Reiser4 is a filesystem that performs all filesystem operations
> > as atomic transactions, which means that it either performs a
-

(edited Kconfig by hand and compiled successfully)