Sorry for the intrusion - just curious what the purpose of this project/task is? Is there a performance benefit? Or are you doing it for some other reason?

Speaking only for myself, fun and learning.

Worsel

Worsel: tested your patch for "test_glibc", it worked just now.

Concerning the reason why I'm doing it: just learning.

Fun and learning are the best motivators I think. If the fun stops or you think there is nothing more to be learnt, that is when innovation stops.

Nobodino,

First the good news: I adapted your latest script to build slackware64-current, using sources downloaded 2014/04/18.
The build ran to completion showning no errors. Also it boots and runs.

Now the bad news:
1. Had to add "export LD_LIBRARY_PATH="/lib64:/usr/lib64" near the top of sfsbuild1.sh to get ghostscript to build.
2. Had to add the patch "jadetexbuild.patch" to sfsinit.sh to get jadetex to build. Did you really build
slackware without this patch? If so, the build works differently on 32 bit vs 64 bit.
3. Have to hit "^C" to complete the boot. It's geting late here so I'll look into this tomorrow.
4. Also cannot connect to the internet. "ifconfig eth0" returns an error message about 'not finding the device'.

Still a good job. Thanks

Worsel

Worsel:

1: maybe could you try these new files included: just put them in an empty $LFS directory and execute: ./sfsinit.sh (it should be compatible with x86_64, to be tested)
2: no patch needed
3: didn't hit "^C" to complete the boot
4: no more errors with ifconfig.

Nota:
The sfsinit contains also the patches.
No more ch6prep: included in sfsbuild1.sh
You may have soon two options: slackware and dlackware (not complete for the time being)

Attached Files

	sfsbuild1.sh.txt (26.1 KB, 41 views)
	sfsinit.sh.txt (86.0 KB, 35 views)

new update.
Should be compatible with slackware and dlackware.
Should build on x86 and x86_64.

Attached Files

	README-sfsd-v24042016.txt (14.1 KB, 47 views)
	sfsinit.sh.txt (91.5 KB, 44 views)
	sfsbuild1.sh.txt (26.8 KB, 39 views)

Nobodino,

I just tried your new scripts. Sfsbuild1.sh quits when it tries to build jadetex.
The following error message appears:

It's too late to try again tonight, but in the two previous versions, applying the
"jadetexbuild.patch" allowed it to continue. I still don't understand why you are
not having the same problem, but that's life. . . .

Worsel

could you provide the patch for jadetex, I could include it in case x86_64?

tetex is a two pass building,
insert : "source /etc/profile/tetex.sh" just before ". $CWD/jadetex.build" in the tetex.SlackBuild

Thought I had already sent a copy, but can't find it. So much for my memory. . .
The patch is attached.

Attached Files

jadetexbuild.patch.sh.txt (413 Bytes, 49 views)

Redownload sfsbuild1.txt there was a bug in.

Haven't you tried modifying tetex.SlackBuild as I suggested (add 'source /etc/profile.d/tetex.sh' before the line '$CWD/jadetex.build ? tetex builds in two pass.

Okay, I'll try again. Here it is.

No, I haven't tried that. The patch worked, so I just used it. Will look into your suggestion.

Attached Files

jadetexbuild.patch.sh.txt (413 Bytes, 42 views)

Worsel:
ok, your patch works, my suggestion doesn't. I just this morning in a x86_64 slackware system.

Nobodino,

I had some problems with booting the kernel after building with your scripts.
The problem seemed to be resolved when I patched sfsinit.sh.

The attached patchfile shows what I did. Look at lines 317 through 367.

Attached Files

sfsinit64.diff.txt (17.3 KB, 47 views)

Carrying on further, I attempted to build X.

Problem 1: The documentation is missing from the source. I scanned the ChangeLogs but
found no mention of this. Is it really gone, Pat, or is it mishap?

Problem 2: The patch, llvmSB.patch did not take and I built 1 1/2 llvm's before I noticed
the second one was being built with gcc also. It's after midnight here so I will look into
it tomorrow or tuesday.

Advice for the day: Do not, repeat Do not start tarring a large directory while building llvm