2.6.16-rc3-mm1: i386 compilation broken

[Adrian Bunk]

On Tue, Feb 14, 2006 at 01:41:57AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.16-rc2-mm1:
>...
> +x86_64-fix-string.patch
>...
>  x86_64 tree updates.
>...

This patch breaks the compilation on i386:

<--  snip  -->

...
  LD      .tmp_vmlinux1
arch/i386/kernel/built-in.o: In function 
`show_type':intel_cacheinfo.c:(.text+0x768b): undefined reference to `strcpy'
:intel_cacheinfo.c:(.text+0x769d): undefined reference to `strcpy'
:intel_cacheinfo.c:(.text+0x76af): undefined reference to `strcpy'
:intel_cacheinfo.c:(.text+0x76c1): undefined reference to `strcpy'
kernel/built-in.o: In function `prof_cpu_mask_read_proc':profile.c:(.text+0x4a84): undefined reference to `strcpy'
kernel/built-in.o:clocksource.c:(.text+0x17bc1): more undefined references to `strcpy' follow
drivers/built-in.o: In function `zoran_write':zoran_procfs.c:(.text+0x41edd6): undefined reference to `strchr'
drivers/built-in.o: In function `cpia_read_proc':cpia.c:(.text+0x42d175): undefined reference to `strcpy'
:cpia.c:(.text+0x42d34c): undefined reference to `strcpy'
:cpia.c:(.text+0x42d35c): undefined reference to `strcpy'
:cpia.c:(.text+0x42d4d7): undefined reference to `strcpy'
:cpia.c:(.text+0x42d5df): undefined reference to `strcpy'
drivers/built-in.o:cpia.c:(.text+0x42d8b9): more undefined references to `strcpy' follow
make: *** [.tmp_vmlinux1] Error 1

<--  snip  -->


Andi, you should have known that your patch could breaks i386 now that 
we are no longer using no-unit-at-a-time:
  http://lkml.org/lkml/2004/11/8/284


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/