From: John Baldwin <jhb@freebsd.org>
To: Kamil Rytarowski <n54@gmx.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org, coypu@sdf.org
Subject: Re: [PATCH v2 0/2] Various build fixes for NetBSD
Date: Mon, 04 Sep 2017 17:08:00 -0000 [thread overview]
Message-ID: <4495676.UmTHkmBAkE@ralph.baldwin.cx> (raw)
In-Reply-To: <93094170-b92c-1360-00d9-682fcf3d448b@gmx.com>
On Monday, September 04, 2017 04:35:58 PM Kamil Rytarowski wrote:
> On 04.09.2017 16:01, Pedro Alves wrote:
> >
> > On 09/04/2017 02:04 PM, Kamil Rytarowski wrote:
> >> On 04.09.2017 14:50, Pedro Alves wrote:
> >>> On 07/25/2017 05:50 PM, John Baldwin wrote:
> >>>> Relative to the first patch series: one patch has been committed,
> >>>> the amd64 KVM support has been dropped, the _KMEMUSER #define was
> >>>> moved earlier in bsd-kvm.o, and the x86 debug registers change was
> >>>> expanded to also add needed object files in the NetBSD/x86 native
> >>>> targets. I haven't been able to test remaining patches so am
> >>>> waiting for testing reports from coypu@.
> >>>>
> >>>
> >>> This hasn't been pushed yet, right?
> >>> FWIW, it looks good to me.
> >>>
> >>> Thanks,
> >>> Pedro Alves
> >>>
> >>
> >> Hi,
> >>
> >> NetBSD patches are still pending. I'm going to readd NetBSD buildbot
> >> after merging them.
> >
> > So, how to break the deadlock? Can you perhaps try applying the
> > patches manually (or John could push them to some branch), and do some
> > quick smoke testing just to be sure things aren't horribly broken?
> > Otherwise, I'd be fine with just pushing them to master directly
> > and if the new buildbot reveals breakage we can always back out the
> > change.
> >
> > Thanks,
> > Pedro Alves
> >
>
> I'm right now upstreaming pkgsrc patches to qemu. Once I will be done, I
> will switch to gdb.
>
> In general there are around 2 remaining build issues on NetBSD
> (<sys/user.h> freebsdism and missing _KMEMUSER). In the past I was
> demotivated by that ChangeLog format.
>
> Long term, I'm still working on ptrace(2) correctness (appropriate
> support for threads in tracee) and LLDB/NetBSD porting.. I expect to
> allocate at some point time - when working on LLDB/kgdb - to improve GDB
> support and resurrect execution of tests.
I'm fine with pushing the current patchset to master if that works best
for you Kamil. I'm also happy to help shepherd NetBSD patches in when I
can.
--
John Baldwin
next prev parent reply other threads:[~2017-09-04 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 16:51 John Baldwin
2017-07-25 16:51 ` [PATCH v2 1/2] Define _KMEMUSER before including BSD kernel headers John Baldwin
2017-07-25 16:51 ` [PATCH v2 2/2] Enable support for x86 debug registers on NetBSD John Baldwin
2017-09-04 12:50 ` [PATCH v2 0/2] Various build fixes for NetBSD Pedro Alves
2017-09-04 13:03 ` Kamil Rytarowski
2017-09-04 14:01 ` Pedro Alves
2017-09-04 14:34 ` Kamil Rytarowski
2017-09-04 17:08 ` John Baldwin [this message]
2017-09-04 13:27 ` John Baldwin
2017-09-04 20:04 ` coypu
2017-09-04 22:18 ` John Baldwin
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=4495676.UmTHkmBAkE@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=coypu@sdf.org \
--cc=gdb-patches@sourceware.org \
--cc=n54@gmx.com \
--cc=palves@redhat.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