From: Russell King <rmk@arm.linux.org.uk>
To: Andy Pfiffer <andyp@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jsimmons@infradead.org
Subject: Re: [TRIVIAL PATCH][2.5.66] fix for link-error in i810fb_imageblit
Date: Tue, 25 Mar 2003 20:18:15 +0000 [thread overview]
Message-ID: <20030325201815.F24418@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1048623198.14000.8.camel@andyp.pdx.osdl.net>; from andyp@osdl.org on Tue, Mar 25, 2003 at 12:13:19PM -0800
On Tue, Mar 25, 2003 at 12:13:19PM -0800, Andy Pfiffer wrote:
> The error:
> ld -m elf_i386 -T arch/i386/vmlinux.lds.s
> arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/built-in.o
> --start-group usr/built-in.o arch/i386/kernel/built-in.o
> arch/i386/mm/built-in.o arch/i386/mach-default/built-in.o
> kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o
> security/built-in.o crypto/built-in.o lib/lib.a arch/i386/lib/lib.a
> drivers/built-in.o sound/built-in.o arch/i386/pci/built-in.o
> net/built-in.o --end-group -o .tmp_vmlinux1
> drivers/built-in.o: In function `i810fb_imageblit':
> drivers/built-in.o(.text+0xb59c1): undefined reference to `__memcpy'
> make: *** [.tmp_vmlinux1] Error 1
>
>
> The diff:
>
> diff -Nru a/include/linux/fb.h b/include/linux/fb.h
> --- a/include/linux/fb.h Tue Mar 25 12:02:29 2003
> +++ b/include/linux/fb.h Tue Mar 25 12:02:29 2003
> @@ -4,6 +4,7 @@
> #include <linux/tty.h>
> #include <asm/types.h>
> #include <asm/io.h>
> +#include <asm/string.h>
>
> /* Definitions of frame buffers */
Why linux/fb.h and why asm/string.h when we have linux/string.h?
Shouldn't <linux/string.h> be included by the i810fb driver?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-03-25 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 20:13 Andy Pfiffer
2003-03-25 20:18 ` Russell King [this message]
2003-03-25 20:49 ` James Simmons
2003-03-25 21:40 ` Andy Pfiffer
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=20030325201815.F24418@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=andyp@osdl.org \
--cc=jsimmons@infradead.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
all inboxes | Powered by JetHome®