From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ed Maste <emaste@freebsd.org>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] Fix FreeBSD (10.x) build after 7dc9ae43
Date: Tue, 22 Nov 2016 10:57:25 +0000 [thread overview]
Message-ID: <20161122105725.GD5970@stefanha-x1.localdomain> (raw)
In-Reply-To: <1479778365-11315-1-git-send-email-emaste@freebsd.org>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Mon, Nov 21, 2016 at 08:32:45PM -0500, Ed Maste wrote:
> Include sys/user.h for declaration of 'struct kinfo_proc'.
> Add -lutil to qemu-ga link for kinfo_getproc.
>
> Signed-off-by: Ed Maste <emaste@freebsd.org>
> ---
> configure | 2 ++
> util/oslib-posix.c | 1 +
> 2 files changed, 3 insertions(+)
Thanks, this looks relevant for QEMU 2.8-rc1 so I applied it to my
staging tree:
https://github.com/stefanha/qemu/commits/staging
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-11-22 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 1:32 [Qemu-trivial] [PATCH] Fix FreeBSD (10.x) build after 7dc9ae43 Ed Maste
2016-11-22 10:57 ` Stefan Hajnoczi [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=20161122105725.GD5970@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=emaste@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).