From: "gboutwel" <gboutwel@praize.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Problems with the SKAS patch and 2.6
Date: 18 Apr 2004 18:55:48 -0000 [thread overview]
Message-ID: <20040418185548.22259.qmail@praize.com> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 1132 bytes --]
> There is a separate version which can be applied like the old
one, i.e. onto
> the kernel + UML patch, in the main UML page.
>
> I applied your slight change to this 2nd version and attached
the result -
> test at least if it applies correctly (this one goes onto the
UML patch).
BlaisorBlade,
I tried this patch. I'm able to compile the host fine, but I've
attached what happens when I try to compile the uml guest.
The steps.
tar jxf linux-2.6.5.tar.bz2
mv linux-2.6.5 linux-2.6.6-rc1
cd linux-2.6.6-rc1
bzcat ~/2.6.4/uml-patch-2.6.4-1.tar.bz2 | patch -p1
cat ~/2.6.6/host+Uml-skas3-2.6.6-rc1-v1.patch | patch -p1
cp ~/2.6.5/config-2.6.5-uml .config
make oldconfig ARCH=um
// I had to modify /arch/um/Makefile-i386 to add the word basic
// after scripts/ like before on 2.6.5
make linux ARCH=um
During the mk_kernel_constants.o, it erros complaining about
a bunch of undefines.
Maybe I'm missing a step or something?
The 2.6.6-rc1 host is doing good though.
George
------------------------------------------
Praize? The all-in-one Christian Community
http://www.praize.com/
[-- Attachment #2: uml-2.6.6-rc1.log --]
[-- Type: , Size: 1435 bytes --]
HOSTCC arch/um/sys-i386/util/mk_sc
CHK arch/um/include/sysdep-i386/sc.h
UPD arch/um/include/sysdep-i386/sc.h
CHK arch/um/include/uml-config.h
UPD arch/um/include/uml-config.h
HOSTCC arch/um/util/mk_constants_kern.o
arch/um/util/mk_constants_kern.c: In function `main':
arch/um/util/mk_constants_kern.c:16: error: `KERN_EMERG' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:16: error: (Each undeclared identifier is reported only once
arch/um/util/mk_constants_kern.c:16: error: for each function it appears in.)
arch/um/util/mk_constants_kern.c:17: error: `KERN_ALERT' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:18: error: `KERN_CRIT' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:19: error: `KERN_ERR' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:20: error: `KERN_WARNING' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:21: error: `KERN_NOTICE' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:22: error: `KERN_INFO' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:23: error: `KERN_DEBUG' undeclared (first use in this function)
arch/um/util/mk_constants_kern.c:25: error: `NSEC_PER_SEC' undeclared (first use in this function)
make[1]: *** [arch/um/util/mk_constants_kern.o] Error 1
make: *** [arch/um/util] Error 2
\r
next reply other threads:[~2004-04-18 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 18:55 gboutwel [this message]
2004-04-19 0:00 ` [uml-devel] Problems with the SKAS patch and 2.6 Jeff Chua
2004-04-19 19:33 ` BlaisorBlade
-- strict thread matches above, loose matches on Subject: below --
2004-04-21 1:11 gboutwel
2004-04-20 16:31 gboutwel
2004-04-16 6:36 Steven Elliott
2004-04-16 8:19 ` Jeff Chua
2004-04-16 17:28 ` BlaisorBlade
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=20040418185548.22259.qmail@praize.com \
--to=gboutwel@praize.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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