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.
I took a look at this. Once the new libxcvt was installed and already-applied patches were removed from x11/patch/xorg-server, it built just fine.
No idea what kind of effect it would have on the blob.
Runs fine, but complains that the drivers have the wrong ABI version.
More than half a dozen drivers won't rebuild against it, including nouveau.
This seems to be exactly the sort of thing to avoid adding while in RC stage.
Well then, perhaps voluntary would be a better default if that's what we had previously...
When I looked into these options a while ago, I came to the conclusion that voluntary is a great option: it adds very little overhead while getting almost all of the gains of full preemption.
As the kernel config says:
Code:
"Voluntary Kernel Preemption (Desktop)"
This option reduces the latency of the kernel by adding more
"explicit preemption points" to the kernel code. These new
preemption points have been selected to reduce the maximum
latency of rescheduling, providing faster application reactions,
at the cost of slightly lower throughput.
This allows reaction to interactive events by allowing a
low priority process to voluntarily preempt itself even if it
is in kernel mode executing a system call. This allows
applications to run more 'smoothly' even when the system is
under load.
Select this if you are building a kernel for a desktop system.
Edit: Debian and Fedora both default to voluntary. Arch (I think) goes for full preemption.
I can see points for both. QT is a big project to build and since QT6 projects are going to become more common as time goes on, it would be nice to not need to build it, especially for those with lower powered machines (although, I imagine there will be community builds like the qt5 build Alien had been providing for years). On the other hand, right now, nothing in Slackware uses QT6 and it is not common for Pat to add things like that without something in Slackware using it.
I also like the idea as a fellow small KDE contributor, but I also like to ask to break the Qt everything in each individual submodule. Well, when some patch come to qtbase, you don't need rebuild all following packages(yeah, it depend), also, for using LXC or docker, will be good to have a small Qt package to install, since many programs just use qtbase. For who wonder how many submodules, check here.
Patrick, thanks for accepting the request for Autogroup.
Last edited by gbschenkel; 10-29-2021 at 12:18 AM.
Reason: Thanking Patrick
request to make configfiles /usr/share/pulseaudio/alsa-mixer/paths/*.conf -> conf.new in pulseaudio.
I had to make changes there (found here answer 16 https://askubuntu.com/questions/2794...s-input-volume) to disable the auto adjusting for my microphone as in webrtc conferences my mic
level was changing all the time, and was always on a to low level.
Mic autoadjusting may be adjusted in some applications itself, but not e.g. in jitsi via chrome.
I also like the idea as a fellow small KDE contributor, but I also like to ask to break the Qt everything in each individual submodule. Well, when some patch come to qtbase, you don't need rebuild all following packages(yeah, it depend), also, for using LXC or docker, will be good to have a small Qt package to install, since many programs just use qtbase. For who wonder how many submodules, check here.
Patrick, thanks for accepting the request for Autogroup.
It's an off-topic, but I'm doing individual packages of QT6-6.2.1 and QTTools does not compile on Current, while (QT3D, QCharts, Qtmultimedia, QTSCXML, QBase, QtDeclarative, .... ..), Compil perfectly, do you have an idea, about the problem?
It's an off-topic, but I'm doing individual packages of QT6-6.2.1 and QTTools does not compile on Current, while (QT3D, QCharts, Qtmultimedia, QTSCXML, QBase, QtDeclarative, .... ..), Compil perfectly, do you have an idea, about the problem?
thanks.
I believe that building Qt6 and packaging it for Slackware is a quite big (and important) endeavor, which deserves its own (mega-)thread.
How about to create one?
Last edited by LuckyCyborg; 10-29-2021 at 03:07 AM.
ap/slackpkg-15.0.8-noarch-1.txz: Upgraded.
Author: piterpunk <piterpunk@slackware.com>
To make it easier to do an unattended slackpkg update/upgrade process,
this commit provides different exit codes for many situations:
0 Successful slackpkg execution.
1 Something wrong happened.
20 No package found to be downloaded, installed, reinstalled,
upgraded, or removed.
50 Slackpkg itself was upgraded and you need to re-run it.
100 There are pending updates.
If I may make a suggestion here, increase rc with severity.
0 Successful operation, or nothing to be done.
1 Successful operation, but updates are pending
4 Slackpkg was upgraded and a rerun needed.
16 Something really bad happened.
That way the script writer can check for success with a simple $? -lt 4 (or 16)
I don't understand your answer. I suggested to volunteers to submit building stuff to SBo to look at the PKGBUILDs from Arch, as that could help them getting started for "what to package and how". Are you stating that you won't volunteer to do that, or that you won't provide already built packages?
Last edited by Didier Spaier; 10-29-2021 at 06:24 AM.
Reason: Rephrased
I don't understand your answer. I suggested to volunteers to submit building stuff to SBo to look at the PKGBUILDs from Arch, as that could help them getting started for "what to package and how". Are you stating that you won't volunteer to do that, or that you won't provide already built packages?
If someone wants my slackbuilds, I send them, but I have neither the time, nor the desire, to take care of SBO, that I do not use.
I believe that building Qt6 and packaging it for Slackware is a quite big (and important) endeavor, which deserves its own (mega-)thread.
How about to create one?
I have started compile all submodules but like others projects(arch x86-64-v3, webassemby, TPM2.0), I lack of time to go on, because my job and MBA(It's near complete).
Quote:
Originally Posted by gmgf
It's an off-topic, but I'm doing individual packages of QT6-6.2.1 and QTTools does not compile on Current, while (QT3D, QCharts, Qtmultimedia, QTSCXML, QBase, QtDeclarative, .... ..), Compil perfectly, do you have an idea, about the problem?
thanks.
I got the problem with QtTools, but was like with QDoc to build the documentation, for what I saw, is needed build qtbase, then qttools, after qtbase agains for building the docs, if needed. Also I was using another GCC version, that is why I didn't saw any bigger problem.
If this change for Qt6 submodules going on, I would like to have docs and examples on /extra. I ask because I use Qt-Creator(SBO) and often, when I had time, I do a Qt rebuild with docs=enable.
I took a look at this. Once the new libxcvt was installed and already-applied patches were removed from x11/patch/xorg-server, it built just fine.
No idea what kind of effect it would have on the blob.
Runs fine, but complains that the drivers have the wrong ABI version.
More than half a dozen drivers won't rebuild against it, including nouveau.
This seems to be exactly the sort of thing to avoid adding while in RC stage.
Yeah, I'm not surprised to hear any of that. Thanks for looking into it though!
I have started compile all submodules but like others projects(arch x86-64-v3, webassemby, TPM2.0), I lack of time to go on, because my job and MBA(It's near complete).
I got the problem with QtTools, but was like with QDoc to build the documentation, for what I saw, is needed build qtbase, then qttools, after qtbase agains for building the docs, if needed. Also I was using another GCC version, that is why I didn't saw any bigger problem.
If this change for Qt6 submodules going on, I would like to have docs and examples on /extra. I ask because I use Qt-Creator(SBO) and often, when I had time, I do a Qt rebuild with docs=enable.
thanks, but the problem here is that qttools doesn't compil after that qtbase is compiled and installed.
from source/xap/freerdp/freerdp.SlackBuild.
That option adds https://github.com/google/sanitizers...dressSanitizer to the binaries and libraries.
AddressSanitizer should be used only when debugging an application:
* it reimplement malloc() slowing the application by about 2x;
* it adds an hard dependency to libasan.so.
I noticed it while building a software that links libfreerdp.
Since the software I'm building doesn't use/support AddressSanitizer, it will build fine but refuse to start with this error:
Quote:
==21756==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
I can of course LD_PRELOAD=/usr/lib64/libasan.so and get it running, but i don't see a good reason for having to do so.
A quick "ldd /usr/lib64/* | grep asan" shows nothing else is currently linking with it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
