From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] ARCH=um compile error
Date: Thu, 05 Oct 2006 15:12:53 +0000 [thread overview]
Message-ID: <452520F5.7020409@bfs.de> (raw)
In-Reply-To: <31029.196.25.255.210.1160058762.squirrel@krooninfsys.dyndns.org>
ask the internet (aka google). there is a
http://gentoo-wiki.com/HOWTO_User_Mode_Linux
and patch.
re,
wh
Jaco Kroon wrote:
> Hi guys,
>
> Probably not the right place to post this (should probably contact the
> maintainers of UML) but in 2.6.18 the file
> ./arch/um/os/sys-i386/registers.c fails to compile with the following
> compile error:
>
> arch/um/os-Linux/sys-i386/registers.c: In function `get_thread_regs':
> arch/um/os-Linux/sys-i386/registers.c:137: error: `JB_PC' undeclared
> (first use in this function)
> arch/um/os-Linux/sys-i386/registers.c:137: error: (Each undeclared
> identifier is reported only once
> arch/um/os-Linux/sys-i386/registers.c:137: error: for each function it
> appears in.)
> arch/um/os-Linux/sys-i386/registers.c:138: error: `JB_SP' undeclared
> (first use in this function)
> arch/um/os-Linux/sys-i386/registers.c:139: error: `JB_BP' undeclared
> (first use in this function)
>
> Grep'ing for these "symbols" reveals that they're not used anywhere else,
> or declared directly (perhaps declared via pasting of sorts) but I cannot
> locate these declarations.
>
> Any suggestions on how to approach this problem?
>
> Jaco
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/kernel-janitors
>
>
>
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-10-05 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 14:32 [KJ] ARCH=um compile error Jaco Kroon
2006-10-05 15:12 ` walter harms [this message]
2006-10-05 16:42 ` Randy Dunlap
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=452520F5.7020409@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.