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.
I'm finally diving into Slackbuilds. I'm currently re-build KDE using the provided Slackbuild script. One thing that poped in my head though, what does everyone do when patches come out? I have not seen a "patches/source" directory anywhere. Do we go directly to the website to grab the sources? Sorry if this has been discussed before, but I couldn't find anything searching here. Thanks in advance!
I'm subscribed to the security mailing list, so when a mail is sent out to advise of an updated package I go to my favorite mirror, download the new package and upgrade. There is not much point compiling a package on your own machine if your using the official SlackBuild script, unless of course you've tweaked it
I'm subscribed to the security mailing list, so when a mail is sent out to advise of an updated package I go to my favorite mirror, download the new package and upgrade. There is not much point compiling a package on your own machine if your using the official SlackBuild script, unless of course you've tweaked it
Dang...how the heck did I miss that link?? lol And yes, I have modify the script to compile everything at i686.
I have modify the script to compile everything at i686.
i'm not sure, but i don't think this would make a difference for you until you'd recompile glibc at i686 as well as everything else (in the proper order)... and even then, the difference would probably not be noticable considering that the way slackware is compiled already includes the i686 optimizations, it's just that it is compiled in such a way that it won't break compatibility with i486...
if you're on slackware 10.2 (GCC 3.3.x) and you wish to gain performance by recompiling, i'd suggest you compile yourself the GCC 3.4.x from -current and then use that to recompile your 10.2... everything i've read indicates that GCC 3.4.x gives faster binaries than GCC 3.3.x...
also, if you're insane, you could recompile everything at "-O3" instead of the "-O2" which is used for most slackware packages...
i'm not sure, but i don't think this would make a difference for you until you'd recompile glibc at i686 as well as everything else (in the proper order)... and even then, the difference would probably not be noticable considering that the way slackware is compiled already includes the i686 optimizations, it's just that it is compiled in such a way that it won't break compatibility with i486...
if you're on slackware 10.2 (GCC 3.3.x) and you wish to gain performance by recompiling, i'd suggest you compile yourself the GCC 3.4.x from -current and then use that to recompile your 10.2... everything i've read indicates that GCC 3.4.x gives faster binaries than GCC 3.3.x...
also, if you're insane, you could recompile everything at "-O3" instead of the "-O2" which is used for most slackware packages...
just my two cents...
Thanks for that info. I wanted to play around with the script just to learn how things work. I've only noticed a slight improvement on my older box. It is kind of neat though to learn the Slackbuild script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.