diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-11-29 01:33:22 +0100 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-11-29 01:33:22 +0100 |
| commit | 5bd36fdff16871eb7d06fc26cac07e7f2703432b (patch) | |
| tree | b430970a01dfc56b8d41979552999984be5c6dfd /open_issues/libpthread_CLOCK_MONOTONIC.mdwn | |
| parent | 2603401fa1f899a8ff60ec6a134d5bd511073a9d (diff) | |
IRC.
Diffstat (limited to 'open_issues/libpthread_CLOCK_MONOTONIC.mdwn')
| -rw-r--r-- | open_issues/libpthread_CLOCK_MONOTONIC.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/open_issues/libpthread_CLOCK_MONOTONIC.mdwn b/open_issues/libpthread_CLOCK_MONOTONIC.mdwn index 86a613d3..22b2cd3b 100644 --- a/open_issues/libpthread_CLOCK_MONOTONIC.mdwn +++ b/open_issues/libpthread_CLOCK_MONOTONIC.mdwn @@ -103,3 +103,11 @@ License|/fdl]]."]]"""]] <pinotree> it'll be safe when implementing some private __hurd_clock_get{time,res} in libc proper, making librt just forward to it and adapting the gettimeofday to use it + + +## IRC, freenode, #hurd, 2012-10-22 + + <pinotree> youpi: apparently somebody in glibc land is indirectly solving + our "libpthread needs lirt which pulls libphtread" circular issue by + moving the clock_* functions to libc proper + <youpi> I've seen that yes :) |