From: Karl-Michael Schindler <720787@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 720787] Re: Fails to compile on MacOS
Date: Thu, 26 May 2011 23:41:46 -0000 [thread overview]
Message-ID: <20110526234146.13567.52208.malone@gac.canonical.com> (raw)
In-Reply-To: 20110217155227.24793.44929.malonedeb@palladium.canonical.com
Nigel's error is also topic in bug
https://bugs.launchpad.net/qemu/+bug/726962
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/720787
Title:
Fails to compile on MacOS
Status in QEMU:
New
Bug description:
Make fails with:
qemu-thread.c: In function 'qemu_mutex_timedlock':
qemu-thread.c:75: warning: implicit declaration of function 'clock_gettime'
qemu-thread.c:75: warning: nested extern declaration of 'clock_gettime'
qemu-thread.c:75: error: 'CLOCK_REALTIME' undeclared (first use in this function)
qemu-thread.c:75: error: (Each undeclared identifier is reported only once
qemu-thread.c:75: error: for each function it appears in.)
qemu-thread.c:78: warning: implicit declaration of function 'pthread_mutex_timedlock'
qemu-thread.c:78: warning: nested extern declaration of 'pthread_mutex_timedlock'
qemu-thread.c: In function 'qemu_cond_timedwait':
qemu-thread.c:143: error: 'CLOCK_REALTIME' undeclared (first use in this function)
make: *** [qemu-thread.o] Error 1
On Git commit commit 79f2b6fcdb7c06cdce6eccc796f5651f3efb843e
Using "configure --enable-io-thread"
next prev parent reply other threads:[~2011-05-26 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 15:52 [Qemu-devel] [Bug 720787] [NEW] Fails to compile on MacOS Nigel Horne
2011-04-01 18:10 ` [Qemu-devel] [Bug 720787] " Nigel Horne
2011-05-26 23:41 ` Karl-Michael Schindler [this message]
2013-07-26 12:58 ` Peter Maydell
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=20110526234146.13567.52208.malone@gac.canonical.com \
--to=720787@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.