From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 2/2] fix risc64 user_regs_struct conflict with kernel header
Date: Tue, 6 Aug 2019 10:04:28 -0400 [thread overview]
Message-ID: <20190806140428.GV9017@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190806131603.GE22009@port70.net>
On Tue, Aug 06, 2019 at 03:16:03PM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@libc.org> [2019-08-06 09:01:29 -0400]:
> > On Tue, Aug 06, 2019 at 03:15:47PM +0300, Baruch Siach wrote:
> > > On Tue, Aug 06 2019, Rich Felker wrote:
> > > > On Tue, Aug 06, 2019 at 08:51:14AM +0300, Baruch Siach wrote:
> > > >> -struct user_regs_struct {
> > > >> +struct _user_regs_struct {
> > > >
> > > > Does this agree with glibc naming?
> > >
> > > glibc riscv headers do not define user_regs_struct.
> >
> > Not even by including a kernel header that defines it? If so, then the
>
> the glibc sys/user.h is empty on riscv.
>
> user_regs_struct is declared in asm/ptrace.h in linux
> but that's not included into libc headers on riscv.
>
> i think musl's user.h should be empty too.
Good news for once! That's even better.
Rich
next prev parent reply other threads:[~2019-08-06 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 5:51 [PATCH 1/2] fix risc64 conflict with kernel headers Baruch Siach
2019-08-06 5:51 ` [PATCH 2/2] fix risc64 user_regs_struct conflict with kernel header Baruch Siach
2019-08-06 12:10 ` Rich Felker
2019-08-06 12:15 ` Baruch Siach
2019-08-06 13:01 ` Rich Felker
2019-08-06 13:16 ` Szabolcs Nagy
2019-08-06 14:04 ` Rich Felker [this message]
2019-08-06 16:31 ` [PATCH 1/2] fix risc64 conflict with kernel headers Rich Felker
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=20190806140428.GV9017@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).