You might as well build your own scripts as use slackbuilds.org -- check out
this section of one of their scripts:
# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
# Unless $ARCH is already set, use uname -m for all other archs:
*) ARCH=$( uname -m ) ;;
DOCS="COPYING Changes INSTALL README.FAQ README.configure"
if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
In the time you spend re-writing their scripts you could write your own.
Eric Hameleers helped me with scripts some years ago, and perhaps out
of that experience came his Alien's SlackBuild Toolkit
. It has three
types of scripts iirc ... one is just like the slackbuilds.org.
Slackware's a dinosaur in that regard, but will change eventually. If what
I've read over the years is correct, Pat believes there are many old comps,
especially servers, with older CPUs and doesn't want to leave them out.
When producing a binary distro they have to tailor the pkgs, and the distro
kernel(s), to fit the maximum number of computers to keep a user base. If all
the people running Slackware could do what you are wanting, they'd probably
be building their own systems with LFS.