All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Nix <nix@esperi.demon.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] redefinition of `struct ptrace_faultinfo' with uml-2.4.22-4 + skas3
Date: Sun, 09 Nov 2003 21:39:38 -0500	[thread overview]
Message-ID: <200311100239.hAA2dcxD013077@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Wed, 17 Sep 2003 00:44:31 BST." <87brtkuwm8.fsf@amaterasu.srvr.nix>

nix@esperi.demon.co.uk said:
> This has come up before on the lists (first report in late 2002), and
> nobody's ever come up with preprocessed source. Until now. 

This is nasty because the UML tree has to assume that the i386 tree doesn't
have ptrace_faultinfo in it.  Since you applied the host skas patch to your
UML tree, that assumption is broken.

So, for now, I would say that you shouldn't try to build both host kernels and
UML kernels from a tree which has that patch in it.

				Jeff



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2003-11-10  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 23:44 [uml-devel] redefinition of `struct ptrace_faultinfo' with uml-2.4.22-4 + skas3 Nix
2003-09-18 19:31 ` Nix
2003-11-10  2:39 ` Jeff Dike [this message]
2003-11-10  7:35   ` Nix

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=200311100239.hAA2dcxD013077@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=nix@esperi.demon.co.uk \
    --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 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.