From: "André Lämmer" <alaemmer@fh-konstanz.de>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Compiling Kernel 2.6 for ppc32
Date: Tue, 9 Sep 2003 18:17:58 +0200 [thread overview]
Message-ID: <000001c376ed$eef95430$0f21258d@fhkonstanz.de> (raw)
Hi!
I tried to compile the kernel 2.6. test 4 for PowerPC. I used the cross
compile tool chain ELDK V2.1 from Denx http://www.denx.de/. I am not
able to make the kernel, because I get the following error.
In file included from include/asm/system.h:8,
from include/linux/list.h:8,
from include/linux/signal.h:4,
from arch/ppc/kernel/asm-offsets.c:12:
include/linux/kernel.h:10: stdarg.h: Datei oder Verzeichnis nicht
gefunden In file included from include/asm/system.h:8,
from include/linux/list.h:8,
from include/linux/signal.h:4,
from arch/ppc/kernel/asm-offsets.c:12:
include/linux/kernel.h:73: parse error before `va_list'
include/linux/kernel.h:73: warning: function declaration isn't a
prototype
include/linux/kernel.h:76: parse error before `va_list'
include/linux/kernel.h:76: warning: function declaration isn't a
prototype
include/linux/kernel.h:80: parse error before `va_list'
include/linux/kernel.h:80: warning: function declaration isn't a
prototype
make[1]: *** [arch/ppc/kernel/asm-offsets.s] Fehler 1
make: *** [arch/ppc/kernel/asm-offsets.s] Fehler 2
I have no problems to compile the kernel for i386 mit the nativ gcc. Can
it be that the GCC 2.95.4 is to old or is there a missing option?
André
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-09-09 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 16:17 André Lämmer [this message]
2003-09-09 16:49 ` Compiling Kernel 2.6 for ppc32 Dan Kegel
2003-09-09 17:30 ` Wolfgang Denk
2003-09-10 16:08 ` André Lämmer
2003-09-10 16:54 ` Wolfgang Denk
2003-09-10 19:14 ` Shih-Ying Chou
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='000001c376ed$eef95430$0f21258d@fhkonstanz.de' \
--to=alaemmer@fh-konstanz.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).