* Michael Cronenworth: > On 7/18/19 4:05 PM, Florian Weimer wrote: >> Old binaries with a 32-bit time_t will continue to run, but new >> binaries built against a current glibc will always use a 64-bit time_t >> under this approach. > How would this affect Wine's handling of 32-bit PE binaries? I'm > assuming they will also break with this change without much > knowledge of the particular handling of that variable. glibc doesn't ship anything PE, so it's not going to affect that directly. I assume Wine needs 32-bit libraries, and if those are 64-bit time_t only, and Wine use time_t-based interfaces, Wine will need to be ported and make the appropriate conversions when going from PE to the GNU/Linux world. Wine will probably want to do this anyway because native Windows (outside the C/POSIX compatibility library) does not have the Y2038 problem. Since 64-bit time_t ports of Wine already exist, this should not be much of an issue. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
