Slackware from Scratch and X11

worsel · 05-04-2016, 02:18 AM

Nobodino,

Disregard the patch for sfsinit.sh that I sent on 4-30. I was, apparently, not careful enough when
cleaning up after trouble-shooting and got an erroneous result.

The reasons it wouldn't boot was because "make oldconfig" went through without a hitch, instead of asking
if I wanted various things. This meant that the local version value was "" instead of "-smp". The kernel
couldn't find the modules.

Lines 35-42 in the attached file are what I did to correct it. Don't know why the configure process didn't
work right the first time, but the configure files are different for 32 and 64 bit.

Worsel

nobodino · 05-04-2016, 02:29 AM

Worsel:

could you test these new versions:
- change $LFS to $SFS as in your scripts
- just adapt to your $PATH
- remove all personal settings
- created the kernel.SlackBuild64 for x86_64
- builds cleanly on x86
- nota : 2 tools directories : tools and tools_64

nota2: I'll adapt sfsinit.sh with your new patch for kernel.SlackBuild, and see if works ok.

worsel · 05-05-2016, 12:48 AM

Nobodino,

Have you been having any trouble with autoconf, automake, m4, and libtool?

When I finish your previous script, these still refer to /tools/bin, which has been
deleted. When I recompile them, they work properly. I have been unable to
find a reason for this behavior. It could be in your script or in the ch5 build,
or something off in my computer. That really narrows it down

Worsel

nobodino · 05-05-2016, 02:04 AM

make a short build list which stops after gettext building, and build "at hand" the first culprit "libtool" and compare its building with the script with only libtool, and progress until you find or not the culprit?

nobodino · 05-05-2016, 04:04 AM

this time this kernel.SlackBuild works on both environment x86 and x86_64 (just tested this morning), and even in non chroot environment:test it outside $SFS to see the result.

worsel · 05-08-2016, 02:48 AM

Nobodino,

Your latest sfsinit.sh and sfsbuild1.sh seem to work as advertised. I didn't try the
dlackware part. Except for the problem outlined below, everything seemed to be ok.

Still having trouble with autoconf, etc. Most of the ones giving me trouble (perhaps all of them)
are scripts. Instead of the first line in the script being "#! /bin/whatever" it is "#! /tools/bin/whatever".
Doesn't matter if it's a perl, python, or sh script.

It doesn't show up until I try to compile X. The only way I can cure it is to run sfsbuild1.sh, the rebuild the
offending packages.

Guess I'll work on it tomorrow. It's almost midnight here and I need my beauty sleep.

Worsel

worsel · 05-09-2016, 02:24 AM

Nobodino,

I did notice one thing on your scripts. The kernel build place the modules in /lib/modules but also
puts a duplicate directory in /lib. I couldn't see where your script was the cause, so maybe the
problem is in the SlackBuild.

I've narrowed down my problem. Don't know why yet, but I know what is affected. The following packages
are built with "/lib/tools/bin/whatever" built in:

Quote:

d libtool
d bison
d flex
d autoconf
d automake
a grep
ap groff
a gzip
ap texinfo
n openssl
ap man-pages
l glibc

I can cure them by deleting the tools directory and recompiling the packages
in the order shown. Since we're using nearly identical scripts, (My last build
was with your latest using slackware-current dated 2016-05-05), I'm curious as
to why you aren't having the same problem. By the way, it doesn't show up
until one tries to build X.

Worsel

nobodino · 05-10-2016, 02:00 AM

Could you test the building of x86_64 with this build1_s.list.

If your LFS is too new (gzip >1.6, makepkg doesn't like very much: weird messages, same thing for findutils if >4.4.2).

To build a x86_64 system, I had to modify slightly the order of packages, and to build twice some packages to be able to boot.
Concerning the kernel, I've not solved the problem for the time being, but I've two ideas to solve it.

worsel · 05-11-2016, 01:39 AM

Your latest build1_s.list built ok, or, maybe better stated, ran to completion.

Actually, glibc built this time without "/tools/bin/" imbedded in xtrace, but
now find (from findutils) and binutils had to be recompiled at the beginning of
the list from my last sending.

I haven't tried compiling X yet. Will try it tomorrow.

worsel · 05-14-2016, 06:41 PM

Was able to build X all the way through xfce in Nobodino's lists.
The base system was built by Nobodino's sfsbuild1.sh on a 64 bit system.
The sources where slackware64-current, synced 20160505.

Some problems encountered:

1. Had to move xtrans up before xpby and libFS in the build list

2. libva-intel-driver needs "--without-wayland" added to the configure
parameters. Haven't made a patch for this yet.

3. p2c was not changed to p2c-1.22 in Nobodino's script.

4. Tix failed to build. Complained it couldn't find /usr/include/tclInt.h
which was there in plain sight.

5. The rcsSB patch failed to apply, even though it was in Nobodino's script.
Haven't looked into this one yet.

6. A full gcc build (ada, c, c++, fortran, go, java, lto, objc) failed.
The #@$%& thing worked last time I tried it.

Anyway, both blackbox and xfce seemed to work normally. Going to take a
few days off of this now. Got things to do. You know : balance the checkbook,
play with the grandkids, woo the girlfriend, etc.

nobodino · 05-16-2016, 02:46 AM

a new update to the scripts for building "slackware from scratch", the four configurations have been tested on x86/x86_64 with slackware/dlackware, they build and boot correctly.
The kernels are now real packages.
Everything about kernels (headers, modules and kernel) has been moved from sfsinit.sh to sfsbuild1.sh, it's cleaner.
Worsel: concerning the rcs patch, a typo changed the "rcs" in "rsc", that's why it didn't work I looked forward a long time before I found it.

Now I can go on for the second part, build x11/xfce...

nobodino · 05-17-2016, 03:56 PM

sfsinit updated with the patch for libva-intel-driver.

nobodino · 05-18-2016, 06:27 AM

by changing the destination of "others" directory, it got wiped before being used.
This version has the new patch, and "others" is usable for building x11.

nobodino · 05-19-2016, 02:08 AM

Worsel: one step forward

Your problems 1/, 2/, 4/ and 5/ should be solved with this.
It builds up to blackbox with the build2_s.list. Only tested on x86 and slackware, not for dlackware.
Don't forget to exit chroot environment and run ./chroot1.sh to have plain $PATH before building x11.

You can delete /tools directory before building X11, it' not necessary anymore.

error: in chroot1.sh: change the first line to '#!/bin/sh' and not '#!/bin.sh'

nobodino · 05-24-2016, 02:35 AM

new updates:
- builds up to xfce on slackware and dlackware and both architectures x86 and x86_64.

To be tested by someone else.