In the comments section of a previous post I already hinted at the problems I have in getting a Chromium package compiled on 32bit Slackware 14.2.
The issue started with the first stable release of the Chromium 79 sources and in particular with the ‘gn’ tool which is used by Google to generate the ninja build files for Chromium. The ‘gn’ code was updated with C++17 features and that is too modern for the gcc-g++ 5.5.0 compiler package in Slackware 14.2.
For 64bit Slackware 14.2 I was able to build ‘gn’ using the embedded version of libc++ which comes with the Chromium sources. On 32bit I got bitten by linker errors – which I was unable to resolve. They seem to be caused by the fact that on a 32bit system, libgcc provides compatibility code to deal with constructs (like ‘unsigned long long’) that do not fit in a 32bit architecture.
For Slackware-current I could rely on a more modern gcc-g++ version (9.2.0) and that produced working 32bit as well as 64bit packages.
Therefore, you can get packages for the new Chromium 79.0.3945.88 browser from my repository, but on 32bit Slackware 14.2 you’re stuck with the older 78.0.3904.108 version (let’s hope that this will change in future).
A little more than three weeks after the new Disney+ movie streaming service went officially live, the Disney company has added Linux support to their Widevine DRM protection. No more “Error 83”. No more need to install the Windows version of Chrome in Wine. Watching your favorite movies is now possible in the native Linux browsers – both Mozilla and Google based. Firefox will download the Widevine CDM (content delivery module) automatically, Chrome has the support built-in and for my Chromium package and other Chromium-based browsers you;ll have to install my chromium-widevine-plugin package.
I guess that a sufficiently large group of Linux enthusiasts have been complaining. And with success!
Today, icedtea-3.14.0 was released. IcedTea is a software build framework which allows easy compilation of OpenJDK.
The new IcedTea release will build you the latest Java8: OpenJDK 8u232_b09. This release syncs the OpenJDK support in IcedTea to the official October 2019 security fixes that Oracle released for Java. The release announcement in the mailing list for distro packagers has details about all the security issues and vulnerabilities that are addressed.
I have built Slackware packages for the new Java 8 Update 232 and uploaded them already. Please upgrade at your earliest convenience. Java is still widespread which makes it a popular target for vulnerability attacks.
Here is where you can download the Slackware packages for openjdk and openjre:
If you want to compile OpenJDK 8 yourself you will need apache-ant as well, but otherwise the openjdk/openjre packages have no external dependencies.
Note about usage:
My Java 7 and Java 8 packages (e.g. openjdk7 and openjdk… or openjre7 and openjre) can not co-exist on your computer because they use the same installation directory. You must install either Java 7 or Java 8.
Remember that I release packages for the JRE (runtime environment) and the JDK (development kit) simultaneously, but you only need to install one of the two. The JRE is sufficient if you only want to run Java programs (including Java web plugins). Only in case where you’d want to develop Java programs and need a Java compiler, you are in need of the JDK package.
Yesterday I uploaded a new DVD-sized ISO for the Plasma5 variant of Slackware Live Edition based on the liveslakscripts version 1.3.3. The ISO contains Slackware-current “Tue Nov 12 23:08:45 UTC 2019” with my KDE-5_19.11 and boots a Linux 4.19.83 kernel.
Download this ISO file slackware64-live-plasma5-current.iso preferably via rsync://slackware.nl/mirrors/slackware-live/ because that allows easy resume if you cannot download the file in one go.
Extensive documentation on how to use and develop Slackware Live Edition (you can achieve a significant level of customization without changing a single line of script code) can be found in the Slackware Documentation Project Wiki.
Dear all, today I released KDE-5_19.11 and it comes with some upgrades to official Slackware packages. Don’t worry – Pat Volkerding kindly added the shared libraries of the official Slackware packages to aaa_elflibs, so if you have been updating your Slackware-current installation properly then nothing will break when you update Slackware’s exiv2 and LibRaw packages to the newer versions contained in the November release of ‘ktown‘.
Official Slackware package updates for exiv2 and LibRaw will come sometime soon, but it will require Pat to recompile several other packages as well that depend on exiv2 and/or LibRaw. I needed the new exiv2 to compile the latest digikam, so I was pleased with Pat’s cooperation to make this a smooth ‘ktown‘ upgrade for you.
The packages for KDE-5_19.11 are available for download from my ‘ktown‘ repository. As always, these packages are meant to be installed on a full installation of Slackware-current which has had its KDE4 removed first. These packages will not work on Slackware 14.2.
This month’s updates to the ‘deps’ are: qt5 and PyQt5.
Fresh additions are: LibRaw and exiv2. These are stock Slackware packages and the two are being upgraded ahead of Slackware, so that the Plasma5 packages can pick them up. Pat added the shared libs for the older releases to ‘aaa_elflibs’ so that none of the Slackware packages will break when you install this month’s Plasma5 packages.
And I have removed qt5-speech because I overlooked that this is already part of the big qt5 package.
I rebuilt kdelibs in the KDE4 section, just like Pat did for Slackware. This removes hardcoded TLSv1 allowing TLSv1.1 and TLSv1.2.
In applications-extra I updated digikam, kile (finally 3.0 beta 3!), kstars and kdevelop-pg-qt, kdevelop, kdev-php, kdev-python. Due to the new exiv2 and LibRaw I rebuilt krename and krita.
KDE Telepathy is no longer part of my ‘ktown’ distribution of KDE Plasma5.