linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Raj Sarraf <rrs@researchut.com>
To: Richard Weinberger <richard@sigma-star.at>, linux-um@lists.infradead.org
Subject: Re: UML fails to build on arch i386
Date: Fri, 15 Jun 2018 12:20:02 +0545	[thread overview]
Message-ID: <503aeaef9da5dbb58f2c1fb9793eb25cb5ce0bc9.camel@researchut.com> (raw)
In-Reply-To: <2135572.4iMtKPa2p5@blindfold>


[-- Attachment #1.1: Type: text/plain, Size: 1297 bytes --]

Hello Richard,

On Thu, 2018-06-14 at 20:41 +0200, Richard Weinberger wrote:
> > 
> > #ifdef __x86_64__
> >    /* Access TLS data.  */
> >    PTRACE_ARCH_PRCTL = 30,
> > # define PT_ARCH_PRCTL PTRACE_ARCH_PRCTL
> > #endif
> > 
> >    /* Continue and stop at the next syscall, it will not be
> > executed.  */
> >    PTRACE_SYSEMU = 31,
> > #define PT_SYSEMU PTRACE_SYSEMU
> 
> Okay, PTRACE_SYSEMU seems to be part of an enum, that's why UML's
> #ifndef does not
> not protect the #define.
> 
> What libc is this?

This is glibc 2.27 from Debian.

rrs@priyasi:~$ dpkg -S /usr/include/x86_64-linux-gnu/sys/ptrace.h 
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/ptrace.h
12:19 ♒♒♒   ☺ 😄    
rrs@priyasi:~$ apt policy libc6-dev
libc6-dev:
  Installed: 2.27-3
  Candidate: 2.27-3
  Version table:
 *** 2.27-3 900
        900 http://deb.debian.org/debian testing/main amd64 Packages
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
12:19 ♒♒♒   ☺ 😄    



> 
> I think we can remove UML's define check and just assume that every
> system has PTRACE_SYSEMU
> properly defined.
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

  reply	other threads:[~2018-06-15  6:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14  5:16 UML fails to build on arch i386 Ritesh Raj Sarraf
2018-06-14  8:58 ` Ritesh Raj Sarraf
2018-06-14 11:15   ` Richard Weinberger
2018-06-14 15:44     ` Ritesh Raj Sarraf
2018-06-14 18:41       ` Richard Weinberger
2018-06-15  6:35         ` Ritesh Raj Sarraf [this message]
2018-06-15  6:43           ` Richard Weinberger
2018-06-15 11:58             ` Ritesh Raj Sarraf

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=503aeaef9da5dbb58f2c1fb9793eb25cb5ce0bc9.camel@researchut.com \
    --to=rrs@researchut.com \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@sigma-star.at \
    /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;
as well as URLs for NNTP newsgroup(s).