From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 517] New: Can't compile 2.5.66 w/i810fb support
Date: Fri, 28 Mar 2003 19:47:54 -0800 [thread overview]
Message-ID: <51790000.1048909674@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=517
Summary: Can't compile 2.5.66 w/i810fb support
Kernel Version: 2.5.66
Status: NEW
Severity: blocking
Owner: jsimmons@infradead.org
Submitter: tmasoner_33@comcast.net
Distribution: Gentoo
Hardware Environment: P-III/Celeron
Software Environment:
Problem Description: Kernel won't compile with i810 frame buffer support
enabled
Steps to reproduce: Enable Frame Buffer Support -> Intel i810/815 support
Results from make bzImage :
make -f scripts/Makefile.build obj=arch/i386/lib
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
gcc -Wp,-MD,init/.version.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-
prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -
mpreferred-stack-boundary=2 -march=pentium3 -Iinclude/asm-i386/mach-default
- fomit-frame-pointer -nostdinc -iwithprefix include -
DKBUILD_BASENAME=version -DKBUILD_MODNAME=version -c -o init/version.o
init/version.c
ld -m elf_i386 -r -o init/built-in.o init/main.o init/version.o
init/mounts.o init/initramfs.o
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 vmlinux
drivers/built-in.o(.text+0x99032): In function `i810fb_imageblit':
: undefined reference to `__memcpy'
make: *** [vmlinux] Error 1
reply other threads:[~2003-03-29 3:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='51790000.1048909674@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--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®