SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello, just signed up today and this is my first post, I hope it is in the right place. I have just started using Slackware last week and I have to say it is fantastic! After trying Ubuntu, Fedora, and Debian I have settled on Slackware and I'm quite pleased. It really seems to support the ideas and the structure of "old school" distributions from the 90's. I have had no crashes, and with help from Alien Bob (creating a multilib system) and slackbuilds.org, I have been able to get all my software not only up and running, but also running much smoother than any other distro, while learning many new things. Anyways enough jabbering! My question is related to compiling programs from source and specifically the speed of compilation. My PC specs are as follows; Intel Q9400 @ 3.2ghz, 6GB DDR2 800mhz, 3 1TB WD Black HD's, and a GTX260 sp216 896MB running the proprietary NVIDIA driver 310.44. When compiling programs from source I notice I am using only one core. I am actually compiling wine in a terminal as I type this. It is hoping from core to core and using 80-100% of that core while compiling. Can I make gcc, or what ever library is used to compile programs, use more than 1 core in order to compile things more quickly, and is there any way to optimize this process? Wine has now been compiling for more than 30 minutes. I'm not in any rush, just want it to be faster and use my system optimally. Can anyone help me?
I'm not aware of any way other than passing the -j option to make. By the way, I usually use n+1 or n+2 for better core utilization (especially if you have a decent amount of RAM). You'll probably cut 10% off the compile time that way.
if you want to use more than one core (replace the number with the appropriate number for your system, I use -j10 on my 6-core and -j3 on my 2-core), or you use the suggestion from saulgoode.
I do the latter for quite sopme time now and it works great. Be aware that some software will not compile when using more than one core (for example webkitgtk), but usually the package maintainer adds a
to those packages. I never had to manually edit a script for that.
You guys are awesome! Doing exactly what saulgoode said I am currently compiling chromium with the slackbuilds script with all four cores at 100% ! Thank you so much fellas this site is great, cant believe all the responses that came so quickly.