time_t now uses 64-bit on 64-bit systems. This fixes the year 2038 bug for 64-bit Haiku, so we can continue to run it after 2038. This breaks the ABI, so all the 64bit packages were rebuilt.
As Michel points out in the comments, this means Haiku’ll be good until 4 December 292277026596, about in time for the beta release.
Will 292277026596 be the year of the Linux desktop though? </tongueInCheek>
Haiku is not linux in any way. It uses gcc, but thet is about it.
I think you missed the point.
What was the point?
Read the post
You definitely missed the point. No one ever implied Haiku is Linux.
Exactly that.
Hence the question…
(we may have hit the dry “humour” limit early)
Edited 2017-07-10 16:50 UTC
That’s my last attempt at humour on here
Oh no, I welcome to a future “dry-humour-off” when Haiku gets its first release candidate! (-:
Probably going to happen the same year as Windows server in the cloud.
Unfortunately, that one’s already here and is growing rather than staying at 0.0001% as it deserves.
They had to fix it before the release of the V1 final, planned for 2039.
I like your optimism
From what I understand, fixing the Y2038 issue required “breaking” the Application Binary Interface (ABI).
The fix was applied to Haiku-64bit. All applications included in the nightly build were recompiled.
The fix was not applied to Haiku-32bit as this would break compatibility with the BeOS applications still in circulation. It is quite possible that BeOS it-self (and by extension Zeta) have the same issue.
They’ll need to eventually make two ABIs for 32-bit. One will be backwards compatible to allow running old programs that won’t break due to the bug; the other will have a minor change to the ABI only affecting the bug. The easiest way to deal with the bug after 2038 would be to have the time freeze right before the date that wraps around. So old 32-bit programs would get the same date from then on, while 32-bit programs compiled with the new ABI will get the proper date.
Dealing with two ABIs for 32-bit shouldn’t be much of a hassle – both MacOS and Windows have done that a number of times, going as far as to have “FAT” binaries that handle both in the same executable. It’s a kludge, but some problems can only be effectively dealt with by a kludge.
Puh-lease get those folks some Aloe Vera!