> 2012/9/1 Roberto De Ioris <[email protected]>:
>> * NEW INFRASTRUCTURE: modular clocks
>>
>> uWSGI 1.3 can now use multiple clock sources (you can create new clock
>> sources using plugins).
>>
>> Currently there are 3 plugins available:
>>
>> unix (uses time() and gettimeofday())
>> realtime (uses clock_gettime with CLOCK_REALTIME)
>> monotonic (uses clock_gettime with CLOCK_MONOTONIC)
>>
>> the 'unix' one is the default.
>>
>> Embedded-system developers can easily create new clocks optimized for
>> their platforms. Check the simplicity of the monotonic plugin:
>>
>> http://projects.unbit.it/uwsgi/browser/plugins/clock_monotonic/clock_monotonic.c
>
> Latest uWSGI doesn't build if I enable clock_monotonic, it fails to
> link (ubuntu 10.04 64 bit):
>
> *** uWSGI linking ***
> gcc -pthread -o build/uwsgi  core/utils.o core/protocol.o
> core/socket.o core/logging.o core/master.o core/master_utils.o
> core/emperor.o core/notify.o core/mule.o core/subscription.o
> core/stats.o core/setup_utils.o core/clock.o core/init.o core/buffer.o
> core/plugins.o core/lock.o core/cache.o core/queue.o core/event.o
> core/signal.o core/cluster.o core/rpc.o core/gateway.o core/loop.o
> lib/rbtree.o core/rb_timers.o core/uwsgi.o proto/base.o proto/uwsgi.o
> proto/http.o proto/fastcgi.o lib/linux_ns.o core/regexp.o
> core/routing.o core/async.o core/ini.o core/yaml.o core/ldap.o
> core/snmp.o core/sendfile.o core/xmlconf.o core/sqlite3.o
> core/spooler.o plugins/ping/ping_plugin.o plugins/cache/cache.o
> plugins/nagios/nagios.o plugins/rrdtool/rrdtool.o
> plugins/carbon/carbon.o plugins/rpc/rpc_plugin.o
> plugins/corerouter/cr_common.o plugins/corerouter/cr_map.o
> plugins/corerouter/corerouter.o plugins/fastrouter/fastrouter.o
> plugins/fastrouter/fr_events.o plugins/rawrouter/rawrouter.o
> plugins/rawrouter/rr_events.o plugins/http/http.o
> plugins/ugreen/ugreen.o plugins/signal/signal_plugin.o
> plugins/syslog/syslog_plugin.o plugins/rsyslog/rsyslog_plugin.o
> plugins/logsocket/logsocket_plugin.o
> plugins/router_uwsgi/router_uwsgi.o
> plugins/router_redirect/router_redirect.o
> plugins/graylog2/graylog2_plugin.o
> plugins/router_basicauth/router_basicauth.o
> plugins/zergpool/zergpool.o plugins/redislog/redislog_plugin.o
> plugins/cheaper_busyness/cheaper_busyness.o
> plugins/router_rewrite/router_rewrite.o
> plugins/router_http/router_http.o
> plugins/clock_monotonic/clock_monotonic.o -lpthread -lm -rdynamic -ldl
> -L/usr/lib -lpcre -lcap -luuid -lyaml -lldap -lssl -lcrypto -lxml2
> -lsqlite3 -lz -lcrypt
> plugins/clock_monotonic/clock_monotonic.o: In function
> `uwsgi_monotonic_microseconds':
> clock_monotonic.c:(.text+0x1d): undefined reference to `clock_gettime'
> plugins/clock_monotonic/clock_monotonic.o: In function
> `uwsgi_monotonic_seconds':
> clock_monotonic.c:(.text+0x6d): undefined reference to `clock_gettime'
> collect2: ld returned 1 exit status
> *** error linking uWSGI ***
>
> Is it issue with my system/settings or bug in uWSGI?
> My buildconf:
>
> [uwsgi]
> debug = false
> inherit = base
> plugins = null
> plugin_dir = build
> bin_name = build/uwsgi
> embedded_plugins = ping, cache, nagios, rrdtool, carbon, rpc,
> corerouter, fastrouter, rawrouter, http, ugreen, signal, syslog,
> rsyslog, logsocket, router_uwsgi, router_redirect, graylog2,
> router_basicauth, zergpool, redislog, cheaper_busyness,
> router_rewrite, router_http, clock_monotonic
>
> --
>

It looks like older systems requires explicit linking with librt.

Retry with the latest tip


-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to