Thanks for the report. Strangely, I was unable to reproduce this on 64-bit FreeBSD 9.1, where I was sure I'd see it.
They're only log messages, so for now I've just casted the two time_t variables to long int. That's a latent Y2K38 problem, but I think we'll want a project-wide solution for that, maybe a PRItime_t macro analogous to the inttypes PRI macros.
andrew
On Mar 16, 2013, at 7:03 AM, Olle E. Johansson oej@edvina.net wrote:
sca_subscribe.c:459: warning: format '%ld' expects type 'long int', but argument 7 has type 'time_t' sca_subscribe.c:459: warning: format '%ld' expects type 'long int', but argument 5 has type 'time_t' sca_subscribe.c:459: warning: format '%ld' expects type 'long int', but argument 6 has type 'time_t' sca_subscribe.c:459: warning: format '%ld' expects type 'long int', but argument 4 has type 'time_t' sca_subscribe.c:459: warning: format '%ld' expects type 'long int', but argument 4 has type 'time_t' sca_subscribe.c: In function 'sca_subscription_print': sca_subscribe.c:679: warning: format '%ld' expects type 'long int', but argument 13 has type 'time_t' sca_subscribe.c:679: warning: format '%ld' expects type 'long int', but argument 11 has type 'time_t' sca_subscribe.c:679: warning: format '%ld' expects type 'long int', but argument 12 has type 'time_t' sca_subscribe.c:679: warning: format '%ld' expects type 'long int', but argument 10 has type 'time_t' sca_subscribe.c:679: warning: format '%ld' expects type 'long int', but argument 10 has type 'time_t'
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev