I think, it is likely to be funny how I'm freaky.

I currently installed Slackware 14.0 (32bit) on my machine.
Before that, to get Slackware installed on my computer,
I had to download totally about 6G in two times.

First time, I downloaded source-code-dvd.iso (3.4G).
I really didn't know what is install-dvd and what is source-code-dvd.
source-code-dvd says that it includes source codes for both of 32bit and 64bit. So, I downloaded that 3.4G torrent file on sleepless nights...haha.
after download, I found that I made mistake.
that's why, second time, I downloaded again slackware-install-dvd.iso (32bit), 2.4G torrent file.

Now, I want slackware-install-dvd.iso (64bit) for my another computer
with 64bit capable cpu.
It is like a nightmare to download another 2.6G torrent file again.

Fortunately (may be), I have slackware-source-code-dvd.iso which I downloaded mistakenly.

So, my question is that:
Is there any way to compile slackware-install-dvd.iso (64bit) out of slackware-source-code-dvd.iso.
If there is a way out there, how can I do it or learn to do it?
If there is no way, what is source-code-dvd.iso for?

I think compiling the whole slackware tree would take more than one day and by then you should be finish downloading the iso for slackware64-14.0

The source code is provided if you need to modify the slackbuild suppose you need additional configure parameter or if you want to learn more aout configuration parameter used to build the program

These is no way to compile the whole source code, some packages won't compile at all (with the new gcc)

To have the source code (you may need it to patch it or just to have a look) and maybe one day we will have a stable gcc :P
But you can safely use 32bit slackware on your 64bit system.

Hello mshlinux,

willysr already covered what the slackware-source-code-dvd.iso is for, and not only would it take to compile many of those programs (and take forever for some), but others fail to build (e.g. xchat).

Even if you did find a patch to make some of the ones that fail to build work (excluding the time it takes to find and/or make these patches), it would still take quite some time to finish.

I honestly think you should just use the 32-bit version (which works fine on 64-bit machines) or download the iso for slackware64-14.0 (if you really want to use the 64-bit version) instead of attempting to use the source code DVD. The only situation I would recommend using the source code DVD is if you have a download rate of 1 byte per second and know for a fact that making the iso from the source code DVD would work flawlessly.

Cheers and happy slacking.

ok!
thanks to all of your posts, I have been able to make a decision.
I am going to download another 2.6G torrent file.
thank u all!

In reality you can compile the system, but I do not recommend it for it would take longer than the download and use up to 1.5 gb of memory during compiling. But if you would like, I will give you instructions on how to do so, just reply asking, my reason: look at my signature.

I'm not the original poster, but would like to know the best way to go about doing it.

If I tried it myself, I'd make a Makefile with make rules for the kernel Makefile and each Slackbuild .. but that would be a lot of effort, and if there's already a recipe out there, I'd rather use it!

Makefiles are typically included with source code, and they're usually what slackbuilds use as part of the process.

For most packages, you can simply run the slackbuild and it'll compile it. You could of course alter the slackbuild if you wanted to add compile time options, etc. But by default they'll produce the binary package you see. on the install discs.

There are of course exceptions as I understand it, but generally speaking that's how you could go about it.

It won't work. Slackware is (at the current state) not a distribution that can be compiled as a whole from scratch, it is a distribution that develops evolutionary. There are packages that without patching or modifying the Slackbuilds won't compile in the current state. See here: http://www.linuxquestions.org/questi...0/#post4771280

1 members found this post helpful.

Creating makefiles with the correct rules is the right way to go, but there is no generic recipe, for it depends on your needs. Figure out the rules you need, create such files, then compile using the terminal. But make sure you copy the contents of the iso to your hard drive first. Plus, you would need to figure out which file makes the dvd bootable, but that can be found by looking at the binary iso. But, you might be wondering, "what is the purpose of the compiling if you already downloaded the binary iso?", the purpose is to fit your specific needs, and possibly edit the source if nessecary.

1 members found this post helpful.

13stein.j: Thank you :-)

s3phir0th115: Yes, but that leaves me with 1014 slackbuild scripts. It's better to have a single makefile with rules for each of those slackbuild scripts (which in turn run make(1) on their own makefiles), else picking up where I left off building things is too tedious. Also, grouping the slackbuild scripts into nested rules is useful for compiling things in parallel which can be (and refrain from compiling things in parallel when they will conflict).

Also, from what AlienBob (by way of TobiSGD) says, there is additional work for some packages in the form of upgrading/patching utilities and libraries which is not included in the slackbuild scripts. Tracking and applying these changes can be incorporated into the top-level makefile as well (especially if different packages require mutually incompatible changes for compilation).

Implementing a top-level makefile like this would be a big chore, essentially encoding a nontrivial chunk of the slackware development team's distro-compiling knowledge. I was hoping 13stein.j already had a recipe for doing it, but alas.

On the other hand, figuring it all out could be fun! :-)

Would you schedule your root canal before, during, or after?

cheers,