SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here should be the one worked on my system. Seems that for some reason the is a missing -j in ./build command for $NUMJOBS
and the path to nspr-config was wrong too.
Code:
--- mozilla-nss.SlackBuild.orig 2020-06-02 15:54:23.818424590 -0300
+++ mozilla-nss.SlackBuild 2020-06-02 16:04:24.014475107 -0300
@@ -93,7 +93,7 @@
-exec chmod 644 {} \+
cd nss
-./build.sh -v $NUMJOBS --opt --system-sqlite --enable-libpkix --disable-tests
+./build.sh -v -j $NUMJOBS --opt --system-sqlite --enable-libpkix --disable-tests
cd -
# Install all the needed stuff to the package dir:
@@ -119,7 +119,7 @@
cd -
# Install nspr-config:
-cat nspr/$(uname -s)*/config/nspr-config | sed -e "s,prefix=/usr/local,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
+cat nspr/Release/config/nspr-config | sed -e "s,prefix=/usr/local,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
chmod 755 $PKG/usr/bin/nspr-config
# Install nss-config:
Intel firmware probably is not the latest, the program spectre-meltdown-checker.sh
said
Code:
* CPU microcode is the latest known available version: NO (latest version is 0x26 dated 2019/11/12 according to builtin firmwares DB v147.20200529+i20200427)
Why would you load FW not published by Intel? And why is Intel "leaking" such FW? Do they need beta testers? Weird.
Intel is moving quite hard in terms of microcode releases for the processor. Plato Mavropoulos extracts the microcode from various sources from different manufacturers e.g. Lenovo, HP, etc.
The microcode version is a production one that is NOT beta.
The spectre-meltdown-checker creator (speed47) also uses this source to check the microcode version (I posted the link to my discussion with him).
I have spoken with ASUS technical support repeatedly asking them to update the microcode for the processor when they release new BIOS versions, once I managed to convince them after a few months but now I gave up and update version myself.
The situation is the same for Intel CSME. Many manufacturers refuse to upgrade the version of Intel ME for their older systems, e.g. my problem with ASUS where I sent the motherboard for RMA and received an identical one without updating the version of Intel ME (I had clearly specified that it was vulnerable).
I had to manually update the version of Intel ME using the Intel tool, FWUpdate according to the instructions here: https://www.win-raid.com/t596f39-Int...tem-Tools.html
Warning!
Updating the microcode version does not involve any risk if it is done from initrd.
Updating the version of Intel ME is more risky involves reading the information presented in the link, understanding exactly what you have to do (including choosing the correct version), checking the status of Intel ME with utilities provided by Intel and then you can try. If something goes wrong you will need an SPI programmer.
Why not put the Alien Bob KDE5 Frameworks packages, which is above Qt5, in the vanilla current Slackware ?
The packages have a size of 79827 Ko. So it is not very big. On my 5 computers with the current Slackware and KDE4, the KDE5 frameworks libraries are installed and I have no problems with them.
Some applications like Kaffeine 2 compile well with them.
It could be a step towards having KDE 5, well studied by Alien Bob and his Ktown set, in the vanilla current Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.