> The main exception comes down to Steam and some games still being x86 32-bit although there is the option of using Flatpak packages or similar containerized solutions for those needing i686 software/apps.
I left macOS for Fedora when they removed the 32bit libs. Had to run lots of simulations on 32bit for embedded arm32, which I didn't wanted to run under qemu. (Tried debian first, but this was a clusterfuck. worse than windows)
Well, let's see what I can do now. linux is not as locked down as macOS, and providing my own multilib gcc and libs should be trivial.
If you need 32 bit support, your best bets are going to be Windows or NetBSD. Most other OSes are phasing it out.
Windows can't kill 32 bit support because even today a significant amount of software for the platform still depends on it, and that won't change any time soon.
NetBSD won't kill it, because support for tons of architectures and platforms is pretty much the reason why it exists. It supports platforms far more exotic and obsolete than 32 bit x86.
Secret to smoothest usage of /usr[/local]/lib64 is to leverage Redhat's
config.site
Intensive details:
config.site is the usual way this works on most distros. They do provide suggestions for a workaround: Basically backport whatever Fedora's config.site does.
FWIW, the distro I'm currently using where this works does this by exporting CONFIG_SITE in /etc/profile.d/site.sh:
In the Linux space it’s used more broadly as shorthand for software built for 32bit only x86 platforms inclusive of P4, and early “Core” branded processors
10 comments
[ 1.9 ms ] story [ 32.7 ms ] threadThis seems like a reasonable work around.
Losing the ability to run these easily is a significant loss for game preservation.
Well, let's see what I can do now. linux is not as locked down as macOS, and providing my own multilib gcc and libs should be trivial.
Windows can't kill 32 bit support because even today a significant amount of software for the platform still depends on it, and that won't change any time soon.
NetBSD won't kill it, because support for tons of architectures and platforms is pretty much the reason why it exists. It supports platforms far more exotic and obsolete than 32 bit x86.
https://wiki.archlinux.org/title/Official_repositories
config.site is the usual way this works on most distros. They do provide suggestions for a workaround: Basically backport whatever Fedora's config.site does.
FWIW, the distro I'm currently using where this works does this by exporting CONFIG_SITE in /etc/profile.d/site.sh:
Source link:https://github.com/egberts/easy-admin/issues/1
For anyone else, this refers to 32 bit Pentium 2/3/Pro architecture