Slackware from Scratch and X11

hendrickxm · 03-14-2016, 02:42 AM

Thanks, great stuff. I managed to use a livecd, added tar-1.13 and the installpkg script. Then used installpkg --root /mnt/chroot *.txz and chrooted into it.
Now I will rebuild in the chroot.
Do you have the packages and slackbuilds you have used and build and can you share them?

Compared to LFS, what packages are absolutely needed to have a system that is capable to rebuild itself. I see elflibs, aaa_base, pkgtools, etc, bin, net-tools, perhaps sudo, curl, openssl, ...?

nobodino · 03-14-2016, 05:10 AM

Read the memos called *-first and *-second I already posted, the minimum is explained to be able to build sfs and remove 'tools'.I noticed you forgot 'which'. By the end of *-second memo, you should be able to remove 'tools',boot in your new sfs and build everything. I hope the answer is clear for you?

worsel · 03-15-2016, 01:56 PM

Nobodino,

Just read over your latest. Looks good. The only questions I had
were minor nitpicks. Managed to answer them myself. Keep up the
good work.

worsel · 03-17-2016, 03:09 PM

Nobodino,

An apology. . .In the last batch of scripts I inadvertently sent the original sfsinit.sh instead of the debugged one.
You seem to have accomodated it, but . . . .

Attached are a corrected sfsinit.sh, an new build5.list, and sfsbuild5.sh.

The sh is the beginning of collapsing all my sh's down to one or two.
Build5.list is the X system broken out to individual files. Hope I got them all

nobodino · 03-18-2016, 01:27 AM

"Attached are a corrected sfsinit.sh, an new build5.list, and sfsbuild5.sh?"
Sorry, I don't see any attached file.

worsel · 03-18-2016, 01:45 AM

Huh, wonder what happened?
They were there when I hit the send button.

Oh, well, here they are. . .

nobodino · 04-04-2016, 12:43 AM

Another update to Slackware From Scratch.
I simplified the process and merged the different steps (sfsbuild0 to sfsbuild4) and there's only one build.list to achieve the build process.
There's less tricks: a real kernel-header package, adjust, sfselflibs are treated as package.
It works on the last current slackware version 01/04/2016 and LFS version 13/03/2016.

archfan · 04-04-2016, 11:54 AM

Thanks for putting this information out there. Really useful stuff. I'm gonna use this to finish my Slackbuild musl build in the near future.

+1

bormant · 04-04-2016, 05:02 PM

@nobodino

don't use # in middle of multiline command as in patches-sfs.sh

Code:

@@ -70,7 +70,7 @@
 ../bootstrap \
   --prefix=/usr \
   --docdir=/doc/$PKGNAM-$VERSION \
-  --qt-gui \
+#  --qt-gui \
   --system-curl \
   --system-expat \
   --no-system-jsoncpp \
@@ -87,7 +87,7 @@
   ../configure \
   --prefix=/usr \
   --docdir=/doc/$PKGNAM-$VERSION \
-  --qt-gui \
+#  --qt-gui \
   --system-curl \
   --system-expat \
   --no-system-jsoncpp \
EOF

# breaks command. You can test:

Code:

#!/bin/sh
echo \
  --1 \
  --2 \
# --3 \
  --4 \
  --5

Code:

$ sh tst.sh
--1 --2
tst.sh: line 7: --4: command not found

The line after # is a new command.

worsel · 04-04-2016, 08:03 PM

Nobodino,

Please check scripts-sfs.sh.txt. When I run it, I don't get the same
results that you show in the README file. Otherwise looks great.
I've been slowly working on something like this, but have had limited
time for it. Keep up the good work!

Worsel

nobodino · 04-07-2016, 12:15 PM

Test with these files.
Only 3 scripts remains: initsfs.sh (and not sfsinit.sh), ch6prep.sh and sfsbuild1.sh.
All other scripts are secondary scripts called by the 3 ones above.

worsel · 04-10-2016, 01:46 AM

Nobodino,

I haven't had much time recently for this, but I did review your latest.
Looks good. Haven't been able to try it yet.

The attachment is something I cooked up while waiting for my car to be
repaired. It goes back to LFS and builds a tools directory using only
Slackware64 current sources, except for check and dejagnu.

nobodino · 04-17-2016, 09:06 AM

Another update to Slackware From Scratch.
It works on the lastet current slackware version 15/04/2016 and LFS version 12/04/2016.
The file for the patches has not changed.
This time , the process is a bit different, no more sub-scripts.
The 3 scripts are built with procedures: one to init, one to chroot, one to build, and that is all.
The differences are in the details, so look carefully.

nobodino · 04-19-2016, 01:46 AM

error in README to build sfs:
time (./sfsbuild1.sh build1.list) # don't forget the build1.list

worsel · 04-21-2016, 04:49 PM

In your script, sfsbuild1.sh, you question why the glibc tests don't work.

Quote:

test-glibc )
# doesn't work, doesn't wait for the answer??
test_1
answer
test_2
answer
test_3
answer
test_4
answer
test_5
answer
test_6
answer
test_7
answer ;;

It doesn't work because you are already redirecting stdin. Can't do it
again in the same loop. The attached patch contains one solution:
(amongst other things. I'm doing a 64 bit build where you are doing 32 bit.)

Look at the patch from "LISTFILE =" down. What I did was read the list into
an array, then processed the array instead of trying to reuse stdin. Got the
idea from the "Advanced Bash Scripting Guide", which I believe is available in french.