From: Sean Bruno <sbruno@freebsd.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [FreeBSD] Build Failure, qemu-char.c
Date: Fri, 22 Jan 2016 08:39:03 -0800 [thread overview]
Message-ID: <56A25B27.1040009@freebsd.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Started seeing a build failure after the updates to qemu-char.c
I think clang is not doing something that gcc does implicitly?
qemu-char.c:1843:26: error: use of undeclared identifier 'common'
chr = qemu_chr_alloc(common, errp);
^
qemu-char.c:4265:36: warning: incompatible pointer types passing
'ChardevCommon *' (aka 'struct ChardevCommon *') to parameter of type
'ChardevBackend *' (aka 'struct ChardevBackend *')
[-Wincompatible-pointer-types]
return qemu_chr_open_pp_fd(fd, common, errp);
^~~~~~
qemu-char.c:1838:61: note: passing argument to parameter 'backend' here
ChardevBackend *backend,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQF8BAEBCgBmBQJWolskXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kdR8H/2UBG5pnCSuKexVqBHyn8coF
85aBuXf5/lz/pPdlU1Wp2wmM/i1isoizxoUYit98hBx4xwu/dFh53CQUPbGgYQBx
LoPLkdwavs7bNT7zQ4PeB1Jm4GN7qqK321mOc1GGOmrWkEyl70fGDUUBN1Cjeo7F
EULAaAmzrTadPHx2gaHUiEGABPHfPmwevaRLnSIbhjPbqqrf/gBy1w5LFJoDCBid
/oOUzJBjzAT1pFz5y3ecyomjz+TUdLtd8LShDcwZtPloheDEvst4UyCg0Sp3z/51
xvk06ZRncTr9Ks5Q+dnVDBKkf3Z8KP0RnX4Kq3q1dTJAXAa4pBcutw8Q7B+29tQ=
=75/8
-----END PGP SIGNATURE-----
next reply other threads:[~2016-01-22 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:39 Sean Bruno [this message]
2016-01-22 16:47 ` [Qemu-devel] [FreeBSD] Build Failure, qemu-char.c Peter Maydell
2016-01-22 16:52 ` Sean Bruno
2016-01-22 17:02 ` Daniel P. Berrange
2016-01-22 17:16 ` Sean Bruno
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=56A25B27.1040009@freebsd.org \
--to=sbruno@freebsd.org \
--cc=qemu-devel@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).