GNU bug report logs -
#65423
README-install contains invalid/outdated information about 32 bit time_t compared to NEWS in 9.3
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On 8/21/23 05:51, Osipov, Michael (IN IT IN) via GNU coreutils Bug
Reports wrote:
> in 9.3 year 2038 support with 64 bit time_t was made required [1], here
> on HP-UX this is a bit problematic, but that's not the actual problem.
> The diff between 9.2 and 9.3 [2] says how this can be fixed on platforms
> supporting both 32 and 64 bit, on HP-UX it'd be simply '+DD64', and how
> to avoid with "ac_year2038_required=no", but README-install on master
> [3] still contains '--disable-year2038' which obviously does not work.
> It simply needs to be updated to the content of [2].
Sorry, I don't understand. Why does --disable-year2038 not work on HP-UX
for bleeding-edge coreutils on Savannah?
It sounds like you're suggesting that we revert the attached patch, but
I don't see how that would be correct as bleeding-edge
coreutils/configure no longer looks at ac_year2038_required.
> I cannot compile everything in 64 bit mode since no one has written our old applications with portability in mind. It needs to remain 32 bit for now.
I suggest compiling coreutils in 64-bit mode now. You can keep compiling
your other applications in 32-bit mode. Even though HP-UX's end of life
is the end of 2025, it's possible you'll run across a stray HP-UX file
today with timestamp after 2038, and basic coreutils apps like 'ls'
should work with such files.
[0001-doc-adjust-build-instructions-for-disabling-year-203.patch (text/x-patch, attachment)]
This bug report was last modified 1 year and 270 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.