GNU bug report logs -
#65423
README-install contains invalid/outdated information about 32 bit time_t compared to NEWS in 9.3
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 65423 in the body.
You can then email your comments to 65423 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-coreutils <at> gnu.org
:
bug#65423
; Package
coreutils
.
(Mon, 21 Aug 2023 10:52:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Osipov, Michael (IN IT IN)" <michael.osipov <at> siemens.com>
:
New bug report received and forwarded. Copy sent to
bug-coreutils <at> gnu.org
.
(Mon, 21 Aug 2023 10:52:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Folks,
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].
FTR: 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.
Michael
[1]
https://github.com/coreutils/coreutils/commit/ffd62ab92c259d513a419b4078a45f1c658dc774
[2]
https://github.com/coreutils/coreutils/compare/v9.2...v9.3#diff-2646d31b27172b7564edd6b4e2116efd8ee5c0cb5355129e8ef9b53ed0ea01b4
[3]
https://github.com/coreutils/coreutils/blob/20b9a015e5aa05c6ad58bda8e9fa963d217b05e3/README-install#L53-L63
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#65423
; Package
coreutils
.
(Mon, 21 Aug 2023 19:26:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 65423 <at> debbugs.gnu.org (full text, mbox):
[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)]
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#65423
; Package
coreutils
.
(Tue, 22 Aug 2023 08:00:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 65423 <at> debbugs.gnu.org (full text, mbox):
On 2023-08-21 21:25, Paul Eggert wrote:
> 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.
No need to be sorry ;-), I understand where your confusion comes from
and mine. I was talking about changes between 9.2 and 9.3 only. Looking
at the changes you refer are solely on master at [1] and [2] which make
year 2038 support optional again. So no action is required anymore.
>> 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.
I agree, and those are just executables. Regardless of this, HPE says at
least until end of 2025, it is at the end a business decision and I am
doing IT, so not my responsibility ;-). I just make it run. The files we
touch go even back to late 80s.
Please go ahead and close this issue, it will auto-resolve with 9.4.
Michael
[1]
https://github.com/coreutils/coreutils/commit/ba128e628cfa0dd111cf235d965200d1cdf77f52
[2]
https://github.com/coreutils/coreutils/commit/3f942cd03fce1a6cda87018306b50f803f08f350#diff-df1edefd8cc0b27219a375d046251a2e9e87fcef6c23767640f12d0b4f784c76L321
Reply sent
to
Paul Eggert <eggert <at> cs.ucla.edu>
:
You have taken responsibility.
(Tue, 22 Aug 2023 14:13:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Osipov, Michael (IN IT IN)" <michael.osipov <at> siemens.com>
:
bug acknowledged by developer.
(Tue, 22 Aug 2023 14:13:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 65423-done <at> debbugs.gnu.org (full text, mbox):
On 8/22/23 02:58, Osipov, Michael (IN IT IN) wrote:
> So no action is required anymore.
Thanks for confirming that. Closing the bug report.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 20 Sep 2023 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 269 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.