From: Jan-Hendrik Palic <jan.palic@linux-debian.de>
To: linux-kernel@vger.kernel.org
Subject: 2.5.2-pre11 with sched01-H7 doesn't build
Date: Mon, 14 Jan 2002 20:41:52 +0100 [thread overview]
Message-ID: <20020114194151.GA12487@billgotchy.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
Hi ..
I downloeded the linux-2.5.1.tar.bz2 and applied the patch for
linux-2.5.2-pre11 patch and the sched01-H7 patch .. at building I got
this :
make[2]: Entering directory
`/home/palic/Files/Projekte/Kernel/PPC/linux-2.5.2-pre11-sched-01H7/kernel'
gcc -D__KERNEL__
-I/home/palic/Files/Projekte/Kernel/PPC/linux-2.5.2-pre11-sched-01H7/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -D__powerpc__ -fsigned-char
-msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring
-fno-omit-frame-pointer -c -o sched.o sched.c
sched.c:21: asm/sched.h: No such file or directory
sched.c: In function `context_switch':
sched.c:430: warning: implicit declaration of function `enter_lazy_tlb'
sched.c:432: warning: implicit declaration of function `switch_mm'
sched.c: In function `schedule':
sched.c:785: warning: implicit declaration of function
`sched_find_first_zero_bit'
make[2]: *** [sched.o] Error 1
make[2]: Leaving directory
`/home/palic/Files/Projekte/Kernel/PPC/linux-2.5.2-pre11-sched-01H7/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory
`/home/palic/Files/Projekte/Kernel/PPC/linux-2.5.2-pre11-sched-01H7/kernel'
make: *** [_dir_kernel] Error 2
palic@shaun:~/Files/Projekte/Kernel/PPC/linux$ ls
arch CREDITS fs ipc MAINTAINERS mm
REPORTING-BUGS
build Documentation include kernel Makefile net Rules.make
COPYING drivers init lib Makefile~ README scripts
palic@shaun:~/Files/Projekte/Kernel/PPC/linux$ cd .
palic@shaun:~/Files/Projekte/Kernel/PPC/linux$ cd ..
palic@shaun:~/Files/Projekte/Kernel/PPC$
What's wrong?
Thnx
Jan
--
One time, you all will be emulated by linux!
----
Jan- Hendrik Palic
Url:"http://www.billgotchy.de"
E-Mail: "palic@billgotchy.de"
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s: a-- C++ UL++ P+++ L+++ E W++ N+ o+ K- w---
O- M- V- PS++ PE Y+ PGP++ t--- 5- X+++ R-- tv- b++ DI-- D+++
G+++ e+++ h+ r++ z+
------END GEEK CODE BLOCK------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-01-14 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 19:41 Jan-Hendrik Palic [this message]
2002-01-14 20:05 ` Stephan von Krawczynski
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=20020114194151.GA12487@billgotchy.de \
--to=jan.palic@linux-debian.de \
--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®