[Slackbuilds-users] 32-bit fails

[B. Watson]

On Fri, 25 Mar 2022, Ozan Türkyılmaz wrote:

> Looking at the upstream sources, a lot of project simply drops 32 bit
> compiles or tests all too gether.

We've run into that in a few cases in our attempt to fix all the
32-bit fails. In a few cases (pdns, pdns-recursor, heimdal), 32-bit
support is broken because of the y2k38 bug, either by accident or on
purpose.

I went ahead and allowed those 3 to build on 32-bit, because it's only
2022 now.

The y2k38 issue... there's now kernel support for a 64-bit time_t on
32-bit, but AFAICT no support in glibc.

There's also another problem: anything with the y2k38 bug that tries
to validate an SSL cert whose expiration date is past 2038, will
fail. That's the reason heimdal wouldn't build: the code was fine, but
the certs used by the test suite have an expiration date 500 years in
the future...

This looks interesting, though it's from 2015: https://lwn.net/Articles/664800/

> NOt having hardware also adds to this.

Eh, I never heard of an x86_64 CPU that doesn't also support 32-bit
x86. They have the hardware... but they may not have the time (or
desire) to maintain a 32-bit container/VM/chroot for testing 32-bit
builds.

> Debian already at the edge of dropping 32 bit. Wine also started
> working on making 32 bit libs work using 64 bit versions using trunking
> (pretty much how MS did their multi lib system with Windows on
> Windows). We are close to end of an era now.

Didn't know that about Wine, that'll be nice to have when it's
working. No more need for multilib or a VM with a full windows install
just to play a couple of games I bought last century.

I'm assuming SBo will continue to support 32-bit as long as Slackware
does, and no longer.