Folks,
Sorry to bring the thread back from the ashes but this warning did
annoy me to such a great extent that I just submitted a patch to
implement a monotonic clock using Mac OS X's API. Now we can get rid
of this warning.
Cheers,
Eduardo Felipe.
On Sat, Apr 9, 2011 at 6:28 AM, Carsten
I submitted a patch to the mailing list, since I don't have commit
access to SVN.
Was my mail lost on the tubes?
Cheers,
Eduardo Felipe.
On Thu, Apr 28, 2011 at 3:08 PM, Lucas De Marchi
lucas.demar...@profusion.mobi wrote:
On Thu, Apr 28, 2011 at 11:58 AM, Eduardo Felipe
On Thu, Apr 28, 2011 at 11:58 AM, Eduardo Felipe
eduardofelip...@gmail.com wrote:
Folks,
Sorry to bring the thread back from the ashes but this warning did
annoy me to such a great extent that I just submitted a patch to
implement a monotonic clock using Mac OS X's API. Now we can get rid
of
On Fri, 8 Apr 2011 20:10:29 -0700 Dave Ray cl...@jonive.com said:
actually... ecore does only spew it out once... on init. so at worst you get
this complaint once per invocation/run. that's entirely reasonable. i don't see
us removing that.
I agree entirely. MacOS is getting more POSIX by the
On Sat, 9 Apr 2011 03:25:49 -0700 Dave Ray cl...@jonive.com said:
that's not worth worrying about then. it's a good reminder of problems you will
end up facing sooner or later. :) and really.. you will not even MEASURE the
amount of space it takes to log. really. relative to all your other
On my OS ecore runs fine, but spews a warning frequently.
CRI12490:ecore ecore_time.c:170 _ecore_time_init() Platform does not support
clock_gettime. Fallback to unix time.
Everything that uses ecore spews it. Fills up my logs.
Is this printf necessary?
Dave
On Fri, Apr 8, 2011 at 8:40 PM, Dave Ray cl...@jonive.com wrote:
On my OS ecore runs fine, but spews a warning frequently.
CRI12490:ecore ecore_time.c:170 _ecore_time_init() Platform does not
support clock_gettime. Fallback to unix time.
Everything that uses ecore spews it. Fills up my
On Fri, 8 Apr 2011 21:36:39 -0300 Gustavo Sverzut Barbieri
barbi...@profusion.mobi said:
On Fri, Apr 8, 2011 at 8:40 PM, Dave Ray cl...@jonive.com wrote:
On my OS ecore runs fine, but spews a warning frequently.
CRI12490:ecore ecore_time.c:170 _ecore_time_init() Platform does not
support
It's a known issue with Darwin, which MacOS is part of. They haven't had
clock_gettime support for 6+ years.
There are alternative time calls that work on Darwin. but the fallback in ecore
seems to work fine. There are some good discussions on the net, I can post some
ideas for monotonic
On Fri, 8 Apr 2011 18:45:12 -0700 Dave Ray cl...@jonive.com said:
wtf? so 10 years after posix-2001 was standardized (and clock_gettime was
around before that) osx still hasnt caught up? wonderfully primitive OS you
have there :) seriously that clock_gettime is relatively important. things
happen
I agree entirely. MacOS is getting more POSIX by the year :).
But in interest of making e17 a clean experience for other MacOS users now I am
wondering what the best fix is. Can we add a patch for Darwin with an
equivalent clock call?
Or should I just patch EINA logging.
On Apr 8, 2011, at
On Fri, 8 Apr 2011 20:10:29 -0700 Dave Ray cl...@jonive.com said:
I agree entirely. MacOS is getting more POSIX by the year :).
But in interest of making e17 a clean experience for other MacOS users now I
am wondering what the best fix is. Can we add a patch for Darwin with an
equivalent
12 matches
Mail list logo
