How I can Build Slackware From Scratch (by source CDs)?
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.
well i compile the stuff that i use alot and that are big. such as X, kde, my kernel(no big deal) and a few libs. Im sure that you can build all the packages that have a slackbuild. but there are some that are noarch so it would be pointless, such as aaa_base
And, just out of curiosity, why would you want to?
An easier way to accomplish what you want is to pick and chose the packages you want installed at install time. Or after the install, run 'pkgtool' and remove what you don't want.
You CAN do what you want, but you will more than likely run into what the RH/FC users call "Dependency Hell"...Missing libraies,programs, etc.
I would guess that you want to follow the basic guidlines given in the LFS book, substituting in the sources from your Slack 3-4 CDs. For your initial build chain (or whatever it's called), just installpkg the stuff you need (aaa_base, binutils, gcc, etc.). Be sure to read through the whole LFS book (I know, it's long) before you start. This way you'll have an understanding of what's going on.
And, just out of curiosity, why would you want to?
Exactly. Apart from the kernel (and stuff which is not included in Slackware), I use all Pat's binaries. No point re-compiling X, KDE or anything else because in my experience, the benefits of doing so aren't worth the pain.
Exactly. Apart from the kernel (and stuff which is not included in Slackware), I use all Pat's binaries. No point re-compiling X, KDE or anything else because in my experience, the benefits of doing so aren't worth the pain.
Well its not that painful for me. My computer is fast enough that i run the script go out party and then wale up the next morning (read afternoon) and its done.
you don't need one... just use the *.SlackBuild scripts which are provided along with the sources... they are the same scripts that patrick uses to build the official packages...
I'm actually going through something like this now. I installed the base system, development tools, and networking support from my Slackware 8 CD. I've manually upgraded to glibc-2.4 and to a 2.6.16.5 kernel as well as to gcc-4.1-20060407 (since gcc-4.1.0 doesn't adequately support glibc-2.4). I recompiled a BUNCH of stuff (autoconf, and similar, coreutils, findutils, diffutils, etc) and I started building X this morning.
Once I get X up, I'll build enlightenment DR17 and then start building the GTK libraries, etc.
I guess my deviation is I'm upgrading to newer versions of what I'm building when I build them. My machine is slow, so this is a long running process but in the end I should have a very current machine.
Wouldn't you get rather current packages if you upgrade in normal way from Slackware Current?
One good thing in building from source is optimizing possibility. But you said that you have a rather slow machine, so optimizing won't give you significant increase in performance. So why don't you take the easier way?
Wouldn't you get rather current packages if you upgrade in normal way from Slackware Current?
One good thing in building from source is optimizing possibility. But you said that you have a rather slow machine, so optimizing won't give you significant increase in performance. So why don't you take the easier way?
Because I tend to stay far more current than any of the distros. For example, when I get X up and running, I'll install the latest GTK+ toolkit, which is currently 2.8.17. That came out last week. I'll upgrade to 2.6.17 when that comes out and I'm already on 2.6.16.5.
I guess I'm more of a "bleeding edge" kind of guy.
What is the latest version of glibc available in Slackware packages? I'm no glibc-2.4 right now.
I don't build from source for optimization reasons as much as being able to keep my system organized the way I want and being able to more readily and easily keep it current. I don't have any of the annoying dependency issues others tend to have when using pre-built binaries and I keep my system up to date with so much stuff, things build and install easily.
That's pretty much what I do. I'm on glibc-2.4, gcc-4.1.0, binutils-2.16.1, gnome-2.14.0, et. all... I can't stand waiting on packages so I rebuilt the entire thing including an up-to-date toolchain to build from. I've been implementing -fstack-protector in alot of packages as well. Can't play with all the latest and greatest glibc/gcc has to offer on slack-current right now. Actually, you can't do that with any distro except Fedora or one you build yourself.
Well, that is my 'live' running system. A heavily bastardized bleeding edge Slackware I suppose... I dual boot with vanilla Slack as well. Just have some problems here and there compiling older packages with the latest GCC. Fedora CVS has patches to fix all that tho.
LFS/DIY is a great thing to get into. After 3 or 4 times you get bored with it and start mashing distro's together and eventually end up making it your own unique creation. That's where it get's interesting instead of a giant copy/pasting exercise which is basically what LFS becomes after a couple times....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
