From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: atanugul@csee.wvu.edu, user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] building from source
Date: Fri, 1 Oct 2004 21:25:20 +0200 [thread overview]
Message-ID: <200410012125.20048.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <1220.157.182.105.1.1096501625.squirrel@www.csee.wvu.edu>
On Thursday 30 September 2004 01:47, atanugul@csee.wvu.edu wrote:
> Hi!
> I tried building a uml kernel from source.I have a debian 2.6.6 kernel on
> my system. I downloaded a 2.4.26 kernel and a matching uml patch
> (uml-patch-2.4.26-1.bz2) for it.I followed the steps specified in the
> user-mode-linux.
You should use either 2.4.26-3 on a 2.4.26 vanilla kernel or 2.4.24-1 on a
2.4.24 vanilla kernel. All the releases between those two have various
problems. In fact, the 2.4.26-3um patch fixes exactly this problem (which
happens because you enabled CONFIG_SMP).
Bye
> Everything went well till step 5. When I did `make linux
> ARCH=um' I got the following error messages:
> gcc -D__KERNEL__ -I/build/kernel-source-2.4.26/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2
> -U__i386__ -Ui386 -fprofile-arcs -ftest-coverage -g -D__arch_um__
> -DSUBARCH=\"i386\" -D_LARGEFILE64_SOURCE
> -I/build/kernel-source-2.4.26/arch/um/include -Derrno=kernel_errno
> -I/build/kernel-source-2.4.26/arch/um/kernel/tt/include
> -I/build/kernel-source-2.4.26/arch/um/kernel/skas/include -c
> mk_thread_kern.cIn file included from mk_thread_kern.c:3:
> /build/kernel-source-2.4.26/include/linux/sched.h:366: error:
> `CONFIG_NR_CPUS' undeclared here (not in a
> function)/build/kernel-source-2.4.26/include/linux/sched.h:366: error:
> `CONFIG_NR_CPUS' undeclared here (not in a
> function)/build/kernel-source-2.4.26/include/linux/sched.h:528: error:
> `CONFIG_NR_CPUS' undeclared here (not in a function)make[1]: ***
> [mk_thread_kern.o] Error 1 make[1]: Leaving directory
> `/build/kernel-source-2.4.26/arch/um/sys-i386/util'make: ***
> [arch/um/sys-i386/util/mk_thread] Error 2
> Can anyone tell me what i should do?
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-01 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 23:47 [uml-devel] building from source atanugul
2004-10-01 19:25 ` BlaisorBlade [this message]
2004-10-08 0:34 ` atanugul
2004-10-08 9:40 ` 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=200410012125.20048.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=atanugul@csee.wvu.edu \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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