From: Jan Kiszka <jan.kiszka@web.de>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] libacard build error
Date: Thu, 27 Oct 2011 09:33:50 +0200 [thread overview]
Message-ID: <4EA9095E.8080403@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
Hi Alon,
I'm getting this with current qemu.git:
CC libcacard/vcard_emul_nss.o
cc1: warnings being treated as errors
In file included from /usr/include/nss3/pkcs11t.h:1780:0,
from /usr/include/nss3/keythi.h:41,
from /usr/include/nss3/keyt.h:41,
from /usr/include/nss3/pk11pub.h:43,
from /data/qemu/libcacard/vcard_emul_nss.c:21:
/usr/include/nss3/pkcs11n.h:365:26: error: "__GNUC_MINOR" is not defined
Just dumping, haven't looked into details. Any patch to fix this already
queued?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2011-10-27 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 7:33 Jan Kiszka [this message]
2011-10-27 7:56 ` [Qemu-devel] libacard build error Alon Levy
2011-10-27 8:13 ` Jan Kiszka
2011-10-27 8:23 ` Alon Levy
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=4EA9095E.8080403@web.de \
--to=jan.kiszka@web.de \
--cc=alevy@redhat.com \
--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).