From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
To: linuxppc-embedded@ozlabs.org
Subject: compile errors
Date: Thu, 21 Sep 2006 16:35:21 -0500 [thread overview]
Message-ID: <20060921213521.GA19725@beardog.cca.cpqcorp.net> (raw)
Hello,
I tried searching for my error without any luck.
I'm new to PPC and embedded linux so please bear with me. I'm trying to cross-compile
on an x86 host for a PPC 440SP target. I downloaded and installed the ELDK from
Wolfgang Denk's website. I execute:
make ARCH=ppc CROSS_COMPILE=ppc_45xx- menuconfig
and configure, save, and exit. To try and build the kernel I execute:
make ARCH=ppc CROSS_COMPILE=ppc_45xx-
it cranks along for a minute before erroring out with:
ppc_4xx-gcc -m32 -Wp,-MD,arch/powerpc/kernel/.process.o.d -nostdinc -isystem /home/embedded/denx/usr/bin/../lib/gcc/powerpc-linux/4.0.0/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Iarch/ppc -Iarch/ppc/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -Os -fomit-frame-pointer -g -Iarch/ppc -msoft-float -pipe -ffixed-r2 -mmultiple -mno-altivec -mstring -Wa,-m405 -Wdeclaration-after-statement -Wno-pointer-sign -DKBUILD_BASENAME=process -DKBUILD_MODNAME=process -c -o arch/powerpc/kernel/.tmp_process.o arch/powerpc/kernel/process.c
arch/powerpc/kernel/process.c: In function 'set_dabr':
arch/powerpc/kernel/process.c:228: error: 'struct machdep_calls' has no member named 'set_dabr'
arch/powerpc/kernel/process.c:229: error: 'struct machdep_calls' has no member named 'set_dabr'
make[1]: *** [arch/powerpc/kernel/process.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
Any suggestions on what's wrong? I've had the same error on the 2.6.15 kernel provided
with the ELDK as well as kernel.org 2.6.10 and 2.6.16.29. My path points to the
denx directories first and ${CROSS_COMPILE}=ppc_4xx-.
Any help is greatly appreciated.
Thanks,
mikem
reply other threads:[~2006-09-21 21:53 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=20060921213521.GA19725@beardog.cca.cpqcorp.net \
--to=mikem@beardog.cca.cpqcorp.net \
--cc=linuxppc-embedded@ozlabs.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