bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13255
> 
>            Summary: 2.6.27.22 compile errors in setup.c; 2.6.27 compiles
>                     perfect on same .config
>            Product: Other
>            Version: 2.5
>     Kernel Version: 2.6.27.10
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: other_other@kernel-bugs.osdl.org
>         ReportedBy: jason.faulkner@rackspace.com
>         Regression: Yes
> 
> 
> Created an attachment (id=21246)
>  --> (http://bugzilla.kernel.org/attachment.cgi?id=21246)
> .config in which the compilation error occurs
> 
> I have a .config (attached) which compiles on 2.6.27, but doesn't compile on
> 2.6.27.22 -- output follows:
> 
> After some troubleshooting, I've discovered the regression was introduced in
> the 2.6.27.10 release (2.6.27.[10-22] will not compile; 2.6.27.[1-9] will)
> 
> # make
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   SYMLINK include/asm -> include/asm-x86
>   CC      arch/x86/kernel/asm-offsets.s
>   GEN     include/asm/asm-offsets.h
>   CALL    scripts/checksyscalls.sh
>   HOSTCC  scripts/genksyms/genksyms.o
>   HOSTCC  scripts/genksyms/lex.o
>   HOSTCC  scripts/genksyms/parse.o
>   HOSTLD  scripts/genksyms/genksyms
>   CC      scripts/mod/empty.o
>   HOSTCC  scripts/mod/mk_elfconfig
>   MKELF   scripts/mod/elfconfig.h
>   HOSTCC  scripts/mod/file2alias.o
>   HOSTCC  scripts/mod/modpost.o
>   HOSTCC  scripts/mod/sumversion.o
>   HOSTLD  scripts/mod/modpost
>   HOSTCC  scripts/kallsyms
>   HOSTCC  scripts/conmakehash
>   HOSTCC  scripts/bin2c
>   CC      init/main.o
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   CC      init/do_mounts.o
>   CC      init/do_mounts_initrd.o
>   LD      init/mounts.o
>   CC      init/initramfs.o
>   CC      init/calibrate.o
>   LD      init/built-in.o
>   HOSTCC  usr/gen_init_cpio
>   GEN     usr/initramfs_data.cpio.gz
>   AS      usr/initramfs_data.o
>   LD      usr/built-in.o
>   CC      arch/x86/kernel/process_64.o
>   CC      arch/x86/kernel/signal_64.o
>   AS      arch/x86/kernel/entry_64.o
>   CC      arch/x86/kernel/traps_64.o
>   CC      arch/x86/kernel/irq_64.o
>   CC      arch/x86/kernel/time_64.o
>   CC      arch/x86/kernel/ioport.o
>   CC      arch/x86/kernel/ldt.o
>   CC      arch/x86/kernel/setup.o
> arch/x86/kernel/setup.c: In function âsetup_archâ:
> arch/x86/kernel/setup.c:714: error: implicit declaration of function
> âvmi_activateâ
> make[1]: *** [arch/x86/kernel/setup.o] Error 1
> make: *** [arch/x86/kernel] Error 2


I can't reproduce this problem with your .config file.
I tried both 2.6.27.10 and 2.6.27.22 and they both built
successfully.  And in looking at the stable 2.6.27.10 patch,
I don't see any problem with it (regarding vmi_activate()).

Did you download the linux-2.6.27.zz.tar.{bz2,gz} tarball
or did you apply some patch(es) to linux-2.6.27 or what?

This was 2.6.27 --> 2.6.27.8 --> (reverse .8) --> 2.6.27 --> 2.6.27.22

Something might have messed up? I'm about to pull the full tarball, and give it a shot with my .config -- it could also be something with my toolchain (although I'm using RHEL5 specific stuff).

Marking this invalid. It works fine on a 2.6.27.22 clean tarball. Must have been some sort of issue while patching.

Thanks!