@ledeuns @miyuru Oh great, another #distro with broken #MultiLib that @fuchsiii has to account for...
The bit-rot of 32bit Linux
Interest of software developers in the use of their product on 32bit Operating Systems has been declining for years. Build tests are only done on 64bit OS'es nowadays. For obvious reasons: there are not so many computers left in the Western world that only support 32bit software.
The thing is, there's still a lot of old co
https://alien.slackbook.org/blog/the-bit-rot-of-32bit-linux/
#Software #32bit #chromium #developers #libreoffice #multilib #Slackware
Slackware-current has absorbed my multilib gcc and glibc packages
Ever since the birth of 64-bit Slackware in 2009, I have been maintaining a multilib repository. Today, 15 years later, things are changing!
You may know it or not, depending on your age, but I have created 64-bit Slackware from scratch late 2008 and early 2009 as a project
https://alien.slackbook.org/blog/slackware-current-has-absorbed-my-multilib-gcc-and-glibc-packages/
@garpu I hope you like it that I kept the multilib build instead of adopting the new WoW64. Even though it's no longer needed to add multilib for a WoW64 binary, some 32bit Windows applications have issues and 16bit Windows applications won't run at all.
Also, adding #multilib to #Slackware is not a hassle at all.
New #multilib #GCC 13.2.0 for #Slackware -current is finally compiling (there's stuff you don't do while traveling, sorry folks for having to stall your upgrades).
Packages at the usual mirror locations hopefully later today.
Dis tonton Fred, épisode 113 : le multilib https://peertube.fr/videos/watch/1ba45d87-4778-4833-9a6d-a42d6777a438