From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.16-rc3-mm1: i386 compilation broken
Date: Tue, 14 Feb 2006 14:17:15 +0100 [thread overview]
Message-ID: <20060214131715.GA10701@stusta.de> (raw)
In-Reply-To: <20060214014157.59af972f.akpm@osdl.org>
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
next prev parent reply other threads:[~2006-02-14 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 9:41 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 11:07 ` 2.6.16-rc3-mm1 Marc Koschewski
2006-02-14 11:16 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 12:16 ` 2.6.16-rc3-mm1 Sander
2006-02-14 12:46 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 13:17 ` Adrian Bunk [this message]
2006-02-14 13:27 ` 2.6.16-rc3-mm1: i386 compilation broken Andi Kleen
2006-02-14 13:54 ` Michal Piotrowski
2006-02-14 20:23 ` Andrew Morton
2006-02-14 21:05 ` Andi Kleen
2006-02-14 21:08 ` Adrian Bunk
2006-02-15 13:19 ` Roman Zippel
2006-02-15 13:32 ` Andi Kleen
2006-02-14 14:00 ` 2.6.16-rc3-mm1: ISDN_DRV_GIGASET driver Adrian Bunk
2006-02-15 1:57 ` Tilman Schmidt
2006-02-15 22:10 ` Adrian Bunk
2006-02-14 14:33 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-14 20:28 ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 23:26 ` 2.6.16-rc3-mm1 Con Kolivas
2006-02-14 23:38 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-15 2:58 ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 15:22 ` [-mm patch] block/blktrace.c: make blk_trace_cleanup() static Adrian Bunk
2006-02-14 15:23 ` Jens Axboe
2006-02-16 23:28 ` 2.6.16-rc3-mm1 Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060214131715.GA10701@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox