I have succeeded in building X11 under Slackware from Scratch.
It was built in one step and seems to run fine. Blackbox came
up smoothly and there were no problems in the half hour I played
with it.

Still not sure that everything got built, but apparently nothing
vital was left out.

There were a few problems along the way:

1) Some programs, although not all, (didn't make a list ),
needed LD_LIBRARY_PATH="/lib64:/usr/lib64" to find the
libraries.

2) Mesa needs libelf, which doesn't seem to be in -Current.
I used the source package from SW-14.1.

3) I had to recompile m4 and libtool. They thought they
should be in the tools directory which had been deleted.

4) Can't read my own handwriting. Anyway, two files (invocation.cpp
and radeon-elf-util.c) needed "include <gelf.h>" and
"include <libelf.h>" changed to "include <libelf/gelf.h>"
and "include <libelf/libelf.h>" respectively. I'll try to
run them down tomorrow. (It's midnight here in Washington state.)

5) xserver needed libepoxy installed.

6) Also had to recompile glib2 before gtk-pixbuf2 would compile.

The list and scripts I used are attached. If anyone wants to use
them, be careful. They're quite picky about changes and I'm not to
sure that the build order is optimal.

Worsel

Attached Files

	buildx.sh.txt (1.1 KB, 374 views)
	x11-1.sh.txt (1.7 KB, 236 views)
	x11-2.sh.txt (1.5 KB, 135 views)
	build5.list.txt (454 Bytes, 160 views)

This one didn't want to go!

Attached Files

sfsbuildx.sh.txt (866 Bytes, 230 views)

comments:
- nice job!
- 2/ and 4/ did you install elfutils? libelf was for Sl-14.1 and elfutils for Sl-14.2 (current)
- 2/ if you built mesa only once, I think mesa-demo doesn't build. You may build it once, install it and build a second time to have mesa-demo built, and then upgradepkg mesa (maybe a second "x mesa" after "x freeglut" in your build5list?)
- I'm surprised you manage to build "dbus" directly, without the need to modify the SlackBuild and execute "dbus-uuidgen --ensure" to build dbus-glib/dbus-python?
- did you manage to build xcm-0.5.2?
- at the end, everything should compile without a hitch, on x32 version, at least.

Aah, peer review. It's a wonderful thing.

No. Somewhere I missed this one. Looked for it too, when I couldn't fined libelf on the
64 bit system. Probably because I didn't know what to look for. Wonder what else I missed?

Cancel 4) above. With elfutils installed, it should build without modifying the files.
Don't know if a 32 bit build needs the files changed or not.

You are correct. Mesa-demo did not build.

Okay, I missed commenting on this. I did modify dbus per your instructions. "dbus-uuidgen --ensure" was in my scripts somewhere. Must have deleted it
and not noticed. Still dbus-glib & dbus-python seemed to build normally.

Yes, xcm-0.5.2 compiled. At least it made a package that appears to be okay visually. I'll test it later today.

I will correct my system and rebuild X11. Probably won't happen until sometime next week with my schedule.

You should be able to check /tmp/x11-build for any *.failed files to see if anything failed to build.

1 members found this post helpful.

Why didn't I think of this before removing /tmp/x11-build?

Is net-tools working correctly, as it should?
Don't you have that kind of message:

root@darkstar_noob:/tmp# ifconfig
No usable address families found.
socket: Success

Id doesn't compile correctly in slackware as well.

Solution: grab sources from debian net-tools_1.60+git20150829.73cef8a.orig.tar.gz and net-tools_1.60+git20150829.73cef8a-2.debian.tar.xz, apply the patches and it builds and works normally.

SlackBuild modified with:

# debian patches
zcat $CWD/Bug#805377-man-pt_BR-ifconfig.8.patch.gz | patch -p1 --verbose || exit 1
zcat $CWD/Bug#541172-netstat.c-exit-codes.patch.gz | patch -p1 --verbose || exit 1
zcat $CWD/translations.patch.gz | patch -p1 --verbose || exit 1
zcat $CWD/Add_missing_headers.patch.gz | patch -p1 --verbose || exit 1
zcat $CWD/Bug#443075-ifconfig.c-pointtopoint_spelling.patch.gz | patch -p1 --verbose || exit 1
zcat $CWD/Bug#500913-man-en_US-route.8-EXAMPLES-Add-single-route-del.patch.gz | patch -p1 --verbose || exit 1

I've updated the build of "Slackware from scratch" memo. I did it manually this time, didn't use my scripts to see what's new.
It's been built from LFS-7.8 for the first part and slackware-current up to 03/12/2015 for the build of Slackware.
There are fewer patches, but new ones.
Works pretty well.

Attached Files

Slackware from scratch -v06122015-first.txt (16.2 KB, 412 views)

2 members found this post helpful.

Sorry I couldn't get right back to you, but I see you found a solution for net-tools.
Better than mine. I went in and modified "by hand".

Your new memo looks good. I'm going to rebuild mine from "scratch" (No pun intended)
after the 1st of the year. Just as soon as I find time.

I've updated the second part, the building of X11 up to xfce functional.
No problem with building X11, no *.failed package if you respect the correct order described here under.
Couldn't get llvm-3.7.0 to build, get back to 3.6 version.
Very few SlackBuilds modified.

Attached Files

Slackware from scratch -v11122015-second.txt (10.6 KB, 129 views)

2 members found this post helpful.

I've improved the memos to build slackware from scratch. They are rather clean now, I believe.
No more x11 failure, just a few patches included.
The system has complete gcc subsystem, and the xfce environment.
Feel free to test.

Attached Files

	Slackware from scratch -v03022016-first.txt (26.3 KB, 239 views)
	Slackware from scratch -v02022016-second.txt (12.2 KB, 164 views)

3 members found this post helpful.

Looks good, Nobodino.

I modified my scripts to follow your latest. Didn't take much for the first part.
Last night I built the basic system with no problems. In the next couple of days
I'm going to do the X11 section.

Up to installing BlackBox, it seems pretty much the same. Some work to do after that
though.

Please, share your scripts when you've finished the two parts. I'm interested in.

Nobodino,

In your second text you call for a patch to rcs, upstream-260704a916.diff.gz.

I can't seem to locate this patch. Would you be so kind as to provide a link?

TIA,

Worsel

see enclosed diff.

Attached Files

upstream-260704a916.diff.txt (2.8 KB, 120 views)

1 members found this post helpful.