We have two different definitions of TIME_T_MAX one in
lib/util/time.c and one in source3/lib/time.c.
On 64bit machines one is INT32_MAX and the other INT64_MAX,
while both are used in the same build.
This results in all sorts of really ugly problems...
The problem is already fixed in master, but not in the production branches.
Created attachment 5623 [details]
Patches for v3-5
Created attachment 5624 [details]
Patches for v3-4
Pushed to v3-5-test and v3-4-test.
Closing out bug report.