From: Richard Weinberger <richard@sigma-star.at>
To: rrs@researchut.com, linux-um@lists.infradead.org
Subject: Re: UML fails to build on arch i386
Date: Thu, 14 Jun 2018 20:41:37 +0200 [thread overview]
Message-ID: <2135572.4iMtKPa2p5@blindfold> (raw)
In-Reply-To: <fb137ebf865a1160b06ac92cfb601fd68533c787.camel@researchut.com>
Am Donnerstag, 14. Juni 2018, 17:44:37 CEST schrieb Ritesh Raj Sarraf:
> On Thu, 2018-06-14 at 13:15 +0200, Richard Weinberger wrote:
> > > This log missed the main error line:
> > >
> > > CC arch/um/kernel/maccess.o
> > > CC arch/um/kernel/kmsg_dump.o
> > > CC arch/um/kernel/skas/clone.o
> > > In file included from ./arch/x86/um/shared/sysdep/ptrace.h:42:0,
> > > from ./arch/um/include/shared/as-layout.h:38,
> > > from arch/um/kernel/skas/clone.c:11:
> > > ./arch/x86/um/shared/sysdep/ptrace_32.h:16:23: error: expected
> > > identifier before numeric constant
> > > #define PTRACE_SYSEMU 31
> >
> > Hmm, can you please check how PTRACE_SYSEMU is defined in your UAPI?
> >
> > The code is pretty boring:
> > #ifndef PTRACE_SYSEMU
> > #define PTRACE_SYSEMU 31
> > #endif
> >
> > My best guess is that PTRACE_SYSEMU is not a define but something
> > else and then
> > #define fails in an interesting way.
>
> There's nothing much in here either.
> From file: i386-linux-gnu/sys/ptrace.h
> And it is the same code on x86_64 too, where I've been able to
> successfully build it.
>
>
>
> #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?
I think we can remove UML's define check and just assume that every system has PTRACE_SYSEMU
properly defined.
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2018-06-14 18:41 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 [this message]
2018-06-15 6:35 ` Ritesh Raj Sarraf
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=2135572.4iMtKPa2p5@blindfold \
--to=richard@sigma-star.at \
--cc=linux-um@lists.infradead.org \
--cc=rrs@researchut.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox