Multithread compilation doesn't use multicore on 14.1 and -current on multilib.
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.
Certain packages will only build with a single process, but multithreading must actually be coded into the software to utilize it. The 32-bit packages would have to actually be built with support for SMP. Because most 32-bit packages are not built with SMP in mind since several 32-bit CPUs do not support multithreading and SMP, these features are disabled when using 32-bit software.
These explanations don't account for it working with plain su but not with su -. Are you passing the -j 4 on the command line or using an environment variable (MAKEFLAGS?) to pass it down? How is su being invoked? Do you first su to a root prompt and then type make or are you passing make as an argument to su?
There's also something in the man page about - needing to be the last option to su . What if you use (the recommended) -l instead of -?
I have the same exact problem.
When compiling a kernel on a multilib system, I'm forced to use su instead of su - or su -l if I want to see all my cpus going 100%.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Rep:
Quote:
Originally Posted by Linux.tar.gz
I have the same exact problem.
When compiling a kernel on a multilib system, I'm forced to use su instead of su - or su -l if I want to see all my cpus going 100%.
I have a fairly clean install of Slackware 14.1 64 bit with multilib. Just last week I upgraded to the 3.18.2 kernel, and when I did make -j8, all 8 cores were maxed out. I used 'su -', not just 'su', and it worked fine.
Slackware 14.1 64 bit, recently updated via slackpkg
16GB ram
Amd FX 8 core 4GHz cpu
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.