Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
03-26-2006, 04:22 PM
|
#1
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
|
Slackbuild and Patches
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!
|
|
|
03-26-2006, 05:19 PM
|
#2
|
Senior Member
Registered: Oct 2004
Posts: 1,272
Rep:
|
ftp://ftp.slackware.com/pub/slackwar...patches/source
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
|
|
|
03-26-2006, 05:27 PM
|
#3
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
Original Poster
|
Quote:
Originally Posted by phil.d.g
ftp://ftp.slackware.com/pub/slackwar...patches/source
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.
|
|
|
03-30-2006, 12:33 PM
|
#4
|
LQ Guru
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870
|
Quote:
Originally Posted by stormtracknole
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...
just my two cents...
|
|
|
03-30-2006, 09:12 PM
|
#5
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
Original Poster
|
Quote:
Originally Posted by win32sux
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.
|
|
|
All times are GMT -5. The time now is 12:09 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|