I have successfully compiled Slackware from Scratch for Slack64.
(My previous build was for 32 bit)

I used Slackware-current sources from the tree downloaded 2015-11-18.
The only exceptions were the kernel (I used 4.2) and libgpg-error-1.20
(libgpg-1.18 would not compile).

Problems encountered (and comments):
1) Had to pass LD_LIBRARY_PATH to ghostscript to get it to find
/usr/lib64.

2) Had to restrict bin.SlackBuild to '-j 1' to get it to run successfully.

3) Had to add the following sed to jadetex.build, just before make:
sed -ie "s?tex jadetex\.in?latex jadetex.in?" Makefile

4) Added hwdata to build2.list just before libffi. Otherwise,
libffi bombed.

5) Added libtasn1 and p11-kit to build3.list to get gnutls to compile.

6) Kmod, usbutils, fuse, and iptools all built okay. (They gave
problems in the previous -32 bit- build.)

7) svgalib gave problems. . .again. In threeDKit/quickmath.h, lines
63 through 147 were deleted. The definitions there are now
provided in /usr/include/math.h or one of it's include files.

8) Had to get a new computer right in the middle of all this.
May the old one rest in peace! (pieces?)

9) The version of Slackware-current used still uses udev. Conversion
to eudev should be fairly straight forward. ( If Pat reads this
last sentence, he will probably start tearing his hair out )

The scripts and lists I used for this project are in the attached .bz2 file
for those who are interested. They should work with 32 bit Slackware also,
but there might be problems.

Nobidino, you will notice that I used a lot of your ideas in these scripts.
Again, Thanks.

Worsel

Okay, I didn't read the rules. I'll have to reorganize to
send the files. I tried to tar and bzip2 them, but that
doesn't seem to be allowed.

Worsel

Here are the build lists used for building SFS64.

Attached Files

	build1.list.txt (479 Bytes, 76 views)
	build2.list.txt (427 Bytes, 48 views)
	build3.list.txt (536 Bytes, 39 views)
	build4.list.txt (191 Bytes, 29 views)

1 members found this post helpful.

I remember that when trying to compile gcc there were several stages, the first using the resident compiler to obtain the first binary gcc, and then gcc was compiled using itself, and maybe one time again, to get a stable result.
Is this method used to get a slackware distribution ?

Toutatis,

Not really. Go to http://www.linuxfromscratch.org/lfs/view/stable/ and read chapter 1.1.
It provides a good overview of what we're doing. The only difference is, after building the
basic tool chain we build from Slackware sources.

Worsel

1 members found this post helpful.

Here are the remainder of the build programs.

Attached Files

	sfsbuild1.sh.txt (1.5 KB, 40 views)
	sfsbuild2.sh.txt (1.2 KB, 23 views)
	sfsbuild3.sh.txt (2.0 KB, 27 views)
	sfsbuild4.sh.txt (718 Bytes, 21 views)
	build.sh.txt (1.6 KB, 29 views)

1 members found this post helpful.

Okay, the last one.

Attached Files

kernel.sh.txt (1.3 KB, 29 views)

1 members found this post helpful.

Much cleaner job than I did.
A question concerning gcc package: I couldn't get it compiling without modifying to "SlackBuild" only gcc and g++? Did you keep the original SlackBuild or not?
Building X11 in one step will be something interesting, particularly "mesa is a mess" among others.

Congratulations.

Congrats and thanks for sharing !!!

To nobodino:

Yes, I modified the gcc build. Forgot I'd done that. I used Pat's SlackBuild, but commented out everything except c, c++, and fortran
which I use occasionally.

As for a "cleaner job", credit where credit is due. My original attempt was a lot longer and much more messy.
After reading your scripts, I combined your ideas and mine.

I'm going to try to do X11 in one step. We'll see how that goes.

Worsel