Hi! I noticed that 'tar' 1.35 fails to build on hurd-i386. The last build that worked was 1.34.
Is it possible to support >y38k on hurd-i386? If so, ought that be reported as a feature request for upstream tar? If it is not possible, should 'tar' be built with --disable-year2038 on hurd-i386 so that it doesn't FTBFS at least? https://buildd.debian.org/status/fetch.php?pkg=tar&arch=hurd-i386&ver=1.35%2Bdfsg-4&stamp=1771536519&raw=0 checking for -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 option for large files... none needed checking for -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 option for timestamps after 2038... support not detected configure: error: in '/build/reproducible-path/tar-1.35+dfsg': configure: error: could not enable timestamps after mid-January 2038. This package recommends support for these later timestamps. However, to proceed with signed 32-bit time_t even though it will fail then, configure with '--disable-year2038'. /Simon
signature.asc
Description: PGP signature
