From: Ritesh Raj Sarraf <rrs@researchut.com>
To: Richard Weinberger <richard@sigma-star.at>
Cc: linux-um@lists.infradead.org
Subject: Re: UML fails to build on arch i386
Date: Fri, 15 Jun 2018 17:43:55 +0545 [thread overview]
Message-ID: <cfa706bc44986339492f32b63adad36257b43f93.camel@researchut.com> (raw)
In-Reply-To: <2534439.LyGaCr9OWm@blindfold>
[-- Attachment #1.1: Type: text/plain, Size: 1754 bytes --]
On Fri, 2018-06-15 at 08:43 +0200, Richard Weinberger wrote:
> Okay, as expected, the ptrace SYSEMU request code is now an enum.
> Changed by in glibc:
> commit c48831d0eebf876d986919baf2d9240a79192837
> Author: Dmitry V. Levin <ldv@altlinux.org>
> Date: Wed Dec 27 00:54:38 2017 +0000
>
> linux/x86: sync sys/ptrace.h with Linux 4.14 [BZ #22433]
>
> Clone generic linux/sys/ptrace.h, add the following x86-specific
> __ptrace_request constants: PTRACE_GET_THREAD_AREA,
> PTRACE_SET_THREAD_AREA, PTRACE_ARCH_PRCTL, PTRACE_SYSEMU,
> PTRACE_SYSEMU_SINGLESTEP, and PTRACE_SINGLEBLOCK.
>
> [BZ #22433]
> * sysdeps/unix/sysv/linux/x86/sys/ptrace.h: New file.
>
> Does this change make UML build on your host?
>
> diff --git a/arch/x86/um/shared/sysdep/ptrace_32.h
> b/arch/x86/um/shared/sysdep/ptrace_32.h
> index b94a108de1dc..ae00d22bce02 100644
> --- a/arch/x86/um/shared/sysdep/ptrace_32.h
> +++ b/arch/x86/um/shared/sysdep/ptrace_32.h
> @@ -10,20 +10,10 @@
>
> static inline void update_debugregs(int seq) {}
>
> -/* syscall emulation path in ptrace */
> -
> -#ifndef PTRACE_SYSEMU
> -#define PTRACE_SYSEMU 31
> -#endif
> -
> void set_using_sysemu(int value);
> int get_using_sysemu(void);
> extern int sysemu_supported;
>
> -#ifndef PTRACE_SYSEMU_SINGLESTEP
> -#define PTRACE_SYSEMU_SINGLESTEP 32
> -#endif
> -
> #define UPT_SYSCALL_ARG1(r) UPT_BX(r)
> #define UPT_SYSCALL_ARG2(r) UPT_CX(r)
> #define UPT_SYSCALL_ARG3(r) UPT_DX(r)
>
Thank you Richard.
That does fix the build. I built and verified it on i386 and amd64.
Thanks,
Ritesh
--
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
prev parent reply other threads:[~2018-06-15 11:59 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
2018-06-15 6:43 ` Richard Weinberger
2018-06-15 11:58 ` Ritesh Raj Sarraf [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=cfa706bc44986339492f32b63adad36257b43f93.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).