Originally Posted by Infohungry
I am thinking that I am going to try and use a different version just to see because I installed another program and it worked great... Kinda. The system did as it was supposed to but I am still learning and don't know how to quite make the change over from windows and mac to linux. Thanks
It is good that you want to learn how to compile from source, but there is much more to it than...
That will mostly lead you to frustration and disappointment. To use the example at hand, if you do that with apache on a working Slackware system you will likely end up breaking your system and still not have a working apache server - even if you satisfy all the compile errors. Then you may end up asking why Slackware is so screwed up? Kind of like putting high octane gas in your new Mercedes, then asking why it doesn't run!
On any system you need to learn how the basic system works, including it's package system, locations of common files and libraries... how things are done on THAT system. Then if you compile and install within that system's requirements, and philosophy
you will reach Nirvana - particularly on Slackware!
Making the change from some lesser operating system invloves learning the how
and the why
A good place to start is of course the Slackware web site
and explore the various text docs on your installation media. Also be sure to read Slackbook
In particular - read all you can about the Slackware package tools and pay particular attention to the why
of it all as you do - not just the how! Then visit Slackbuilds.org
and have a look at how some of the build scripts work. In no time you will be compiling everything from source - but in a good way!