All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fix x86-64 SLES9 tools build problem...bugzilla #34
Date: Tue, 31 May 2005 10:10:53 -0500	[thread overview]
Message-ID: <1117552253.5056.0.camel@thinkpad> (raw)
In-Reply-To: <1117139085.10510.3.camel@thinkpad>

Why is this patch not in the tree yet? No one seems to have any comments
on it. Folks using SLES9 want it.

On Thu, 2005-05-26 at 15:24 -0500, Jerone Young wrote:
> SLES9 has a problem with it's <asm/elf.h> and other headers associated
> with it. Since we are only using one thing from this (that we really
> don't need) we can just stop including it. Someone speak up if they do
> not think this is a suitable fix.
> http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=34
> 
> Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> 
> --- xc_ptrace_core.c.old        2005-05-26 09:46:39.262113168 -0500
> +++ xc_ptrace_core.c    2005-05-26 10:19:45.731123976 -0500
> @@ -1,7 +1,6 @@
>  #include <sys/ptrace.h>
>  #include <sys/wait.h>
>  #include "xc_private.h"
> -#include <asm/elf.h>
>  #include <time.h>
> 
> @@ -258,7 +257,7 @@ xc_ptrace_core(enum __ptrace_request req
>      case PTRACE_GETFPXREGS:
>         if (request == PTRACE_GETREGS) {
>                 SET_PT_REGS(pt, ctxt[cpu].user_regs);
> -               memcpy(data, &pt, sizeof(elf_gregset_t));
> +               memcpy(data, &pt, sizeof(struct gdb_regs));
>         } else if (request == PTRACE_GETFPREGS)
>             memcpy(data, &ctxt[cpu].fpu_ctxt, sizeof(ctxt[cpu].fpu_ctxt));
>         else /*if (request == PTRACE_GETFPXREGS)*/
> 
> --- xc_ptrace.c.old     2005-05-26 10:15:18.597734424 -0500
> +++ xc_ptrace.c 2005-05-26 10:19:27.347918648 -0500
> @@ -1,7 +1,6 @@
>  #include <sys/ptrace.h>
>  #include <sys/wait.h>
>  #include "xc_private.h"
> -#include <asm/elf.h>
>  #include <time.h>
> 
> 
> @@ -301,7 +300,7 @@ xc_ptrace(enum __ptrace_request request,
> 
>         if (request == PTRACE_GETREGS) {
>                 SET_PT_REGS(pt, ctxt[cpu].user_regs);
> -               memcpy(data, &pt, sizeof(elf_gregset_t));
> +               memcpy(data, &pt, sizeof(struct gdb_regs));
>         } else if (request == PTRACE_GETFPREGS)
>             memcpy(data, &ctxt[cpu].fpu_ctxt, sizeof(ctxt[cpu].fpu_ctxt));
>         else /*if (request == PTRACE_GETFPXREGS)*/
> 
> 
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

  reply	other threads:[~2005-05-31 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 20:24 [PATCH] Fix x86-64 SLES9 tools build problem...bugzilla #34 Jerone Young
2005-05-31 15:10 ` Jerone Young [this message]
2005-05-31 15:32   ` Ryan Harper

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=1117552253.5056.0.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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.