ctf: Use g_time_val_from_iso8601 instead of g_date_time_new_from_iso8601
authorSimon Marchi <simon.marchi@efficios.com>
Thu, 2 May 2019 20:53:30 +0000 (16:53 -0400)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Fri, 3 May 2019 15:16:53 +0000 (11:16 -0400)
commit5ec1bd5c3200e4eb986299bad81d15fc319b60e3
tree08aa9de2b79d86d415b3d9c9d249a3b3ae2c46e3
parentd09947735d101a482b7b51b60487345e9aae91e2
ctf: Use g_time_val_from_iso8601 instead of g_date_time_new_from_iso8601

g_date_time_new_from_iso8601 was introduced in glib 2.56, which is quite
recent.  To support build with older glibs, change the code to use
g_time_val_from_iso8601 instead, introduced in glib 2.12.

The code in question only uses this function to validate that the passed
string is ISO8601-compliant, it doesn't use the resulting time value.

The problem of g_time_val_from_iso8601 is that its result is not year
2038-safe on 32-bit systems.  We can expect that by then, that function
will have been removed from glib, forcing us to update our code.

Change-Id: I2f4fdfce9020ecefcfb5d653a3885d343e49bd76
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1245
Reviewed-by: Michael Jeanson <mjeanson@efficios.com>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
plugins/ctf/fs-sink/fs-sink-trace.c
This page took 0.025257 seconds and 4 git commands to generate.