After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 367894 - glib-2.12.4 glib/gtimer.c:g_timer_elapsed() uses USE_CLOCK_GETTIME && HAVE_CLOCK_GETTIME
glib-2.12.4 glib/gtimer.c:g_timer_elapsed() uses USE_CLOCK_GETTIME && HAVE_CL...
Status: RESOLVED DUPLICATE of bug 353694
Product: glib
Classification: Platform
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2006-10-30 20:23 UTC by Michael O'Keefe
Modified: 2006-12-04 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael O'Keefe 2006-10-30 20:23:56 UTC 
Please describe the problem:
glib-2.12.4/glib/gtimer.c:264 fails to compile if HAVE_CLOCK_GETTIME is defined, but HAVE_MONOTONIC_CLOCK is not.
This is why USE_CLOCK_GETTIME is defined @ glib-2.12.4/glib/gtimer.c:55


Steps to reproduce:
1. have a system that has clock_gettime
2. have a system that doesn't define _POSIX_MONOTONIC_CLOCK in bits/posix_opt.h or CLOCK_MONOTONIC in bits/time.h 
3. this is being cross compiled, so glib_cv_monotonic_clock=no had to be defined in the config cache


Actual results:
Compilation fails

Expected results:


Does this happen every time?
Yes

Other information:
Change glib-2.12.4/glib/gtimer.c:260 to use USE_CLOCK_GETTIME instead of HAVE_CLOCK_GETTIME and it compiles
Comment 1 Shai Seger 2006-11-08 13:15:47 UTC 
Same happened to me. And I did the exact same fix.
Comment 2 Jens Granseuer 2006-12-04 14:28:19 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 353694 ***