re: Slackware from Scratch again
 

Rebuilt Slackware from Scratch, using Slackware-current,
downloaded February 8, 2016. I know there have been
upgrades since, but I like to keep my sources stable
for the duration of a build.

Problems found were:

1. I missed that libarchive had been moved to build list 2
and had to add "--without-archive" to the slackbuild
and rebuild in list 3.

2. Had to build eudev early. Wget would not compile. Disabled
introspection for the first build.

3. Had to rebuild libpng-1.6.20 before cmake would work.

4. The tix patch you gave would not work for me, Nobodino. Don't
know what I was doing wrong. Anyway I went in and removed those
two pesky exclamation marks by hand.

5. Had a hard time finding p2c-1.22. Finally found it on the
Madiera sight. p2-1.22-26.mga6.src.rpm.

6. Doxygen was okay after I wrote my own SlackBuild.

Anything else has been previously covered by myself or Nobodino.

There were a number of other problems, mostly pebkac's. The
biggest one though, was finding time to do this. It was fun however.

Nobodino, my scripts are attached. Also patches for all the
SlackBuilds we change. Enjoy!

Goofed again. Forgot this thing can't tell
one file from another without a suffix.
Oh, Well. . . .:rolleyes:

It looks good to me.
That's what I couldn't do myself: make "nice" scripts with my memos.
I do appreciate the job done.

oups!

Ran into two problems with SFS today.

1. Dialog somehow became linked to libncursessw-6.0. Had to recompile.

I think this happened because I did not delete the tools directory
in time. It probably should be deleted as soon as we build gcc.
Can't see that it should be used after that.

2. Xdm would boot me into root, but not user.

The error message was "XDM authorization key matches an existing
client![fvwm][main]: <<ERROR>> can't open display :0"

A search on the internet led me to a BSD message recommending
slim instead of gdm or kdm. I grabbed it from Slackbuilds.org,
installed it, and lo ... it worked!

On the other hand I got fvwm, firefox, and thunderbird working.

a little improvement to your patches. Just rename the file.txt in file.sh (chmod +x file.sh) and ./file.sh and look at the result.

Okay, I knew about that. Guess I got on a track and
forgot to get off.

Nobodino,

In your bbp20062015.txt, you indicated that both gstreamer and gstreamer0 needed their
SlackBuilds modified. I found the patch for gstreamers0 and blindly (I believe that is
a euphemism for stupidly) applied the patch to both SlackBuilds. If this was not the
intent, please advise.

TIA

no, it was just gtreamer0 which was concerned by the patch.

Otherwise, I rebuild sfs with your scripts and simplify them for my purpose. You will see it.

Slackware from Scratch and X11
 

Rebuilt SFS using slackware64-current dated 2016-03-04.

The only new problem was net-tools. To compile it I had to
build libical and bluez just before net-tools.

I noticed that several X programs complain that doxygen does
not exist. Might it not be a good idea to build doxygen before
building X? I'll test this with my next build.

Concerning net-tools see the new patch file enclosed. You'll know how to use it.

I already succesfully rebuild a fairly minimal slackware install before and the instructions here are very nice.
There is something I would like to try but cannot seem to find out how. I want to install a minimal slackware build and chroot into it and continue building. Meaning to installpkg from a non-slackware host and add all needed packages to rebuild themself.
You could get the same by doing a minimal install, boot a livecd and chroot from there.
Firstly, could someone provide me a list of packages needed for slackware such that the resulting system is able to rebuild itself? Containing enough to have a lfs-like system.
Next question, what would be the easiest way to get pkgtools installed on a non-slackware distro, without untarring slackware packages.

My guess would be to install tar-1.13 and copy the installpkg (and makepkg) script(s) on the host/livecd system.
Minimal list is kinda available in the notes provided by nobodino.

hendrickxm,

Thank you!

For your first question, I don't know that continuing in chroot after my sfsbuild4.sh script (see previous posts in this thread for scripts)j
is wise. (This is equivalent to finishing nobodino's "slackware from scratch -v03022016-first.txt" listing. (also available earlier in this thread).
At this point I reboot into the newly built system. It is fully capable of rebuilding itself at this point.

To continue after this point without rebooting probably requires some sort of virtual machine software. I've no experience with such. For more
info see my post in the bedrock linux forum.

For your second question, I believe your guess is correct. Take care though, programs don't always install smoothly on alien systems!

Thanks for your reply.
My idea is to get pkgtools on a host distro (livecd), install a list of packages (original slackware-current packages), similar as the one nobodino to build the chrooted environment, chroot into the system and rebuild the system, then add up to whatever I need.
And to get pkgtools (actually installpkg is enough) I guess adding tar-1.13 and the installpkg script should do it. If not, I can try with a livecd from zenwalk, slax, salix, ... that has pkgtools.

A new update for "Slackware From Scratch", now the process is rather "automatic". I used Worsel's scripts and adpated them to an x86 system and simplified a little bit. There's no more tricks in the beginning of the process of building, it is clean.
Glibc is built from the beginning.
Tar-1.13 and which are included in "tools" to able to build cleanly the first seeds of slackware: makepkg, etc, aaa_base and glibc.

From now I've just done it for the first part.
You can try it, and if you're as lazy as I am, you just need a "resynced slackware repository", build LFS up to chapter 5 and execute about 10 scripts.