qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Martin Bochnig <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-0.8.2 on glibc 2.2.5: CLOCK_MONOTONIC not defined
Date: Mon, 23 Oct 2006 19:00:55 +0200	[thread overview]
Message-ID: <453CF547.1020004@gmx.com> (raw)
In-Reply-To: <OF6BEDB89D.76B63FB4-ONC1257210.003F5192-C1257210.00401474@codingtechnologies.com>

Wolfgang Schildbach wrote:

>I stumbled upon the same problem as Bill Rossi (see his post below):
>
>The current cvs version of qemu fails to compile on my machine because 
>CLOCK_MONOTONIC is not defined in my glibc. According to clock_gettime(3), 
>systems that define this functionality have _POSIX_MONOTONIC_CLOCK and 
>_POSIX_TIMERS set. Updating the ifdef (see patch below) to include these 
>makes the offending code go away on my CLOCK_MONOTONIC-less system 
>(gcc3.3), but continues to include it on a newer system with a later 
>libgcc. Not sure if the __linux__ in there is still necessary, but I left 
>  
>


The same happens on Solaris(11, but probably all versions).
(Note:  Solaris uses its own libc not glibc.)

A complete merge of opensolaris.org's current QEMU patch
   http://opensolaris.org/os/project/qemu/downloads/  
from 0.8.2 to cvs may follow some time next week.
Two other things needed to be changed for cvs.current to build on
Solaris/SunOS5.x.


Martin Bochnig
at nowhere

      reply	other threads:[~2006-10-23 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 17:38 [Qemu-devel] qemu-0.8.2 on glibc 2.2.5 Bill Rossi
2006-10-23 11:39 ` [Qemu-devel] qemu-0.8.2 on glibc 2.2.5: CLOCK_MONOTONIC not defined Wolfgang Schildbach
2006-10-23 17:00   ` Martin Bochnig [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=453CF547.1020004@gmx.com \
    --to=mb1x@gmx.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).