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.
Thanks, but I won't register to Linkedin for that.
Please post a link to publicly a available web page if any.
I asked the author of the post.
While we wait for the answer I will copy and past his post:
Quote:
Tommaso Bilotta
Rebuild slackware! :-)
Hello friends, I recently wrote a script that changes the SlackBuild and allows you to put flags optimized for the PC. My notebook, ssd disk - OCZ Vertex IV, writes 1.4 GB / Sec with dd from / dev / zero with PF-Kernel. I'd like to start a project to parameterize the SlackBuild in the compiler optimization. The results at the end are great :-). A bit like on freebsd with / etc / make.conf.
This is a part of the script that acts as a patch. Basically looking for a file, for exceptions, if there is no exception for the package for the optimizations, the value assigned to the variable by default.
<non constructive>Recompiling my 1111 packages to get a performance increase I'm no sure that it I will even notice is not on the top of my TODO list</non constructive>
But that could interest some, and probably some slackers did that already. Maybe they could post here how they did it, then?
Maybe the odd package could benefit from targeted recompilation, but I have to agree with Didier. A complete rebuild seems like it wouldn't give a worthwhile return on investment.
If that person were using Google+ to discuss it instead of LinkedIn, I would possibly read it. But I unsubscribed from that Slackware group on LinkedIn long ago because of all the SPAM I got in my mailbox from one of the other members promoting his books.
Anyway, looking at his "/etc/make.conf" perhaps he should have a look at the Alien's ARM project where I am modifying lots of SlackBuild scripts to read a configuration file "/etc/slackbuild/machine.conf". I use that filename and in my SlackBuild script modifications am using a variable definition block which I discussed with Pat and which has his approval (basically he changed a few things to arrive at the final design).
The old style block of code dealing with $ARCH doesn't have to be anywhere near as ugly as it is: The selections in the case statement are duplicated in the if/then/elif/else blocks below it, and then there's that completely unnecessary double call to uname -m)
I use the following construct in my build scripts which is much cleaner.
If you moved any common assignments outside and prior to the case statement and just use the case statement to override them it is shorter still, but i prefer seeing all the assignments for an individual arch in a block of consecutive statements for ease of reading.
Last edited by GazL; 04-07-2013 at 11:00 AM.
Reason: Added -O2 -fPIC to be more representative of a stock package in case anyone cut/pastes
I just tried march=core2 on ffmpeg and MPlayer and it appears to have doubled the cpu utilisation while playing back a vidieo, so I'll be sticking with the defaults in future.
Hello Friends, unfortunately I still have not published anything. Since, however, the topic is of interest, scripts, and reorganized them public on github. The basic idea is that the flags (-O2-march-mtune ... ...) are set by default in a file (make.conf), if there is a file in a specified directory, which is named package these parameters are considered instead of the global ones. By doing so, if a program with the global settings you should fill in (for whatever reason), you can put exceptions ..... An important part, in my opinion, is the iventario packages and the association of each file to the package so that you have absolute control over the operating system. I implemented a script that seemed files in / var / log / packages /
(
cd /var/log/packages/
ls -1 | awk '
{
n=split($0, vett, "-");
. The return them in a sqlite3 database. I was also thinking to run ldd with a list of libraries that every track needs in order to establish, associated with each "I" to the packages dependencies.
If that person were using Google+ to discuss it instead of LinkedIn, I would possibly read it. But I unsubscribed from that Slackware group on LinkedIn long ago because of all the SPAM I got in my mailbox from one of the other members promoting his books.
Anyway, looking at his "/etc/make.conf" perhaps he should have a look at the Alien's ARM project where I am modifying lots of SlackBuild scripts to read a configuration file "/etc/slackbuild/machine.conf". I use that filename and in my SlackBuild script modifications am using a variable definition block which I discussed with Pat and which has his approval (basically he changed a few things to arrive at the final design).
If that person were using Google+ to discuss it instead of LinkedIn, I would possibly read it. But I unsubscribed from that Slackware group on LinkedIn long ago because of all the SPAM I got in my mailbox from one of the other members promoting his books.
Anyway, looking at his "/etc/make.conf" perhaps he should have a look at the Alien's ARM project where I am modifying lots of SlackBuild scripts to read a configuration file "/etc/slackbuild/machine.conf". I use that filename and in my SlackBuild script modifications am using a variable definition block which I discussed with Pat and which has his approval (basically he changed a few things to arrive at the final design).
This is kinda like the make.conf from Gentoo.
This is really cool!
Definitely. Good thing is that SlackBuilds actually doesn't hide the magic, so I can tell what will happen, when and why. This always confuse me on Gentoo as I never know where all variables in ebuilds and init scripts came from.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.