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.
I have be recompiling/optimizing slackware packages for my P4 over the weekend. I managed to do 42 including KDE (KDE took me 20 hours on a 1.8 GHz P4 w/ 256 MB of RAM). Other than KDE I am trying to replace all of those i386 packages first. I am quite happy with my progress and I haven't ran across any problems. NOTE: I am only redoing the ones with .SlackBuilds as opposed to the ones with .Build for now. I'm trying to take baby steps and learn as I go. The SlackBuild scripts are amazing! I really understand all but one thing that I have ran across in a few packages. Here is a little exert from one of the packages for an example.
You could change i486 to s390 and it would mean the same thing.
Don't worry, be happy.....
Anyway, I figured it out on my own. Sorry for wasting you guys time.
TARGET should always equal the specific ARCH that GCC was compiled/optimized for. Out-of-the bow slackware GCC is i486. Until I recompile/optimize GCC for i686 I should not change that entry in the SlackBuild script.
NOTE: I am only redoing the ones with .SlackBuilds as opposed to the ones with .Build for now. I'm trying to take baby steps and learn as I go. The SlackBuild scripts are amazing! I really understand all but one thing that I have ran across in a few packages.
Could you please help me with the following questions?
What are SlackBuild scripts? Are they officially releases with Slackware packages? Where can I find them?
SlackBuild scripts contain all the information that PV uses to build the Slackware release packages. Ie: all the ./configure options and the symlink options in the final package (and whole bunch of other stuff ... ).
They can be found, along with the sources and any referenced patches, on Disks 3 and 4.
In short, you run the .SlackBuild script from within the source directory of whatever (as root in some cases, or with makepkg in your path for most), and you end up with a Slackware .tgz package located (typically) in /tmp !
Read those more than once. Then download the sources. Next look in the source directories (folders) to find those with a file called .SlackBuild or someprogram.SlackBuild. Those are slackbuild scripts. Stay away from those source packages with scripts named .build or someprogram.build. Those are build scripts and not SlackBuilds. Pat is gradually replacing those with slackbuild scripts. They work great however, but some prefer the slackbuild scripts, including Pat, because of the way they work.
My advice, read through the SlackBuild scripts to see how they are made. They are built several different ways depending on the program itself. There are things that you can edit in some slackbuild scripts that you can't in others. Build something small and unimportant first just to learn and get a feel for it before you start rebuilding X11 or glibc. By the way, the first thing I rebuilt was bsd-games!
Originally posted by Basel What does the option do?
Apparently, "--enable-final" concatenates all the source code files into one block before compiling, which means you get a faster compile, and supposedly smaller binaries. Unsurprisingly, this method can be very RAM-hungry.
2. Read it. Observe all warnings if there are any in both the changelog as well as the readme found in the host site where the upgraded packages are stored.
3. Download the upgraded packages. Keep in mind that some packages listed in the change log may have been upgraded more than once and only the latest version may be found in the "current" directory. You may want to scan over the changelog and note where packages have been upgraded more than once before you download anything.
use the [upgradepkg] command in a terminal to upgrade it.
su to assume root
Move to the directory where you stored the upgraded package
root@darkstar# cd /place-where-you-stored-the-upgraded-package.
Next run upgradepkg [in this example I will use "qt-3.3.4" as found in KDE
root@darkstar# upgradepkg qt-3.3.4-i486-2.tgz
you could also do this to upgrade everything at once
root@darkstar# upgradepkg *.tgz
But you may not want to, espically if you find warnings in the changelog stating that some packages need to be upgraded in a certain order.
Also keep in mind that some packages upgraded will work better if you reboot the system after upgrading the package.