> I believe these are the two cases: > > - The public 'struct curl_fileinfo' contains a time_t struct member, used for > FTP wildcard callbacks. > > - The public API curl_getdate() takes a time_t pointer in its second argument. > > If 'time_t' changes size, those two will not be ABI compatible.
Interestingly, the latter is the only one picked up by ABI compliance checker: https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/compat_reports/libcurl4-openssl-dev/lfs_to_time_t/compat_report.html And because the time_t pointer argument to getdate is unused we could _probably_ get away with ignoring that (a bit sketchy from a purity point of view but I think ok in practice). OTOH the former (presumably not found because the "curl_fileinfo" type is not found in any public ABI) looks like a genuine ABI break to me. Hopefully there are not too many "hidden" ABI breaks like this lurking!
