From: Jeff Dike <jdike@addtoit.com>
To: Murali Nagaraj <muralin@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] linux-2.6.16 build broken?
Date: Wed, 7 Jun 2006 22:15:25 -0400 [thread overview]
Message-ID: <20060608021525.GB5567@ccure.user-mode-linux.org> (raw)
In-Reply-To: <835bb2cb0606060553q6402b169p19e9b37bdec5fa16@mail.gmail.com>
On Tue, Jun 06, 2006 at 05:53:08PM +0500, Murali Nagaraj wrote:
> CC arch/um/os-Linux/sys-i386/registers.o
> 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)
Apply this patch - we are figuring out a real way to fix this:
http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.17-rc5/patches/jmpbuf
Jeff
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2006-06-08 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 12:53 [uml-devel] linux-2.6.16 build broken? Murali Nagaraj
2006-06-08 2:15 ` Jeff Dike [this message]
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=20060608021525.GB5567@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=muralin@gmail.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