Slackware from Scratch and X11

worsel · 03-31-2018, 09:50 PM

Quote:

I'm still screwd with:
----------------------------
tar (child): lzip: Cannot exec: Too many levels of symbolic links
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
---------------------------

I've read over your script and can't see anything that should cause these problems.

Just a long shot, but in your select statement, use some other word than build:

"select usraction in go-on quit
do "

worsel · 04-01-2018, 01:03 AM

Follow up on my last post. I just ran the most recent scripts that you posted.
(well, started them anyway

)

So far all is well. Just starting glibc now.

nobodino · 04-01-2018, 03:14 AM

the problem is when:
- first time: you choose "old", and you build, everything is ok.
- second time: you choose "new", and you try to boostrap a new SFS.

nobodino · 04-02-2018, 03:13 AM

Regression test on slackware64-current (Sun Apr 1 02:53:26 UTC 2018):

Strange failure for "xfce4-panel-4.12.2".

If you build xfce in one batch with the script xfce-build-all.sh it will fail on xfce4-panel: it doesn't see exo installed (see build.log)
-----------------------------
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for exo-1 >= 0.7.2... not found
*** The required package exo-1 was not found on your system.
*** Please install exo-1 (atleast version 0.7.2) or adjust
*** the PKG_CONFIG_PATH environment variable if you
*** installed the package in a nonstandard prefix so that
*** pkg-config is able to find it.
ls: cannot access '/tmp/xfce4-panel-*txz': No such file or directory
----------------------------
If you build it a second time with the same script it will build everything.
On the second pass, it will see it (see second build.log)
----------------------------
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for exo-1 >= 0.7.2... 0.12.0
checking EXO_CFLAGS... -pthread -I/usr/include/exo-1 -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/xfce4 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
checking EXO_LIBS... -lexo-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lxfce4util -lglib-2.0
checking for pkg-config... (cached) /usr/bin/pkg-config
----------------------------

If you build everything by hand each of the package listed in xfce-build-all. sh script it will build normally: xfce4panel will see exo installed??

Everything else ok.

worsel · 04-03-2018, 03:00 PM

Quote:

Strange failure for "xfce4-panel-4.12.2".

I had noticed this using your scripts from 2018-03-13, but thought it was
from some changes I made.

Wonder if it has something to do with this: https://alien.slackbook.org/blog/

elcore · 04-06-2018, 01:12 AM

Is there somewhere a list of packages which attempt to access network resources at build time?

For example alsa-utils-1.1.6 I had to build with flag --disable-xmlto or else it would try to access a remote location.

The build machine should not have to require network access, that is just bad. IMO it's trading security for convenience.

worsel · 04-06-2018, 11:23 PM

Quote:

Is there somewhere a list of packages which attempt to access network resources at build time?

Not that I know of. You might try grepping the slackbuilds for wget, etc.

nobodino · 04-07-2018, 12:53 AM

the first package needing access network see sfsbuild1 is "esound":
------------
esound )
dhcpcd -t 10 eth0 && updatedb
build $SRCDIR $PACKNAME
[ $? != 0 ] && exit 1 ;;
-------------
after that the access to network is established.

elcore · 04-07-2018, 01:24 AM

Quote:

Originally Posted by worsel

Not that I know of. You might try grepping the slackbuilds for wget, etc.

Well it's no problem with SlackBuilds, I always read the packaging script and network dependency is not very common.
But when compressed sources are shipped incomplete and require remote resource, that's when there's a problem.

nobodino · 04-07-2018, 12:34 PM

I found the culprit for "the too many symlinks".

worsel · 04-07-2018, 08:27 PM

Quote:

I found the culprit for "the too many symlinks".

Good work. I missed it reading that script and should have seen it.
This is the reason I usually delete the link, then remake it when
I change the tools directory.

nobodino · 04-08-2018, 03:36 AM

Actually, something is broken in -current (since >= 30032018), pkg-config or something else: procps-ng and util-linux don't see "libncursesw.so.6" and I don't what broke this? So I can't even build build1_s.list, I will have to dig in http://cgit.notk.org/adrien/slackwar...t.ext.git/log/ ...

worsel · 04-08-2018, 06:51 PM

Quote:

Actually, something is broken in -current (since >= 30032018),. . . .

Yes, Current (64 bit) gets to procps in build1_s.list. The following error(s) were returned.

Quote:

/tools/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find libncursesw.so.6
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:1434: watch] Error 1
make[2]: *** Waiting for unfinished jobs....
libtool: link: gcc -std=gnu99 -Iproc -O2 -fPIC -o lib/test_strutils lib/test_strutils.o lib/strutils.o -ldl
libtool: link: gcc -std=gnu99 -Iproc -O2 -fPIC -o lib/test_fileutils lib/test_fileutils.o lib/fileutils.o -ldl
libtool: link: gcc -std=gnu99 -Iproc -O2 -fPIC -o lib/test_nsutils lib/test_nsutils.o lib/nsutils.o -ldl
make[2]: Leaving directory '/tmp/procps-ng-3.3.13'
make[1]: *** [Makefile:1837: all-recursive] Error 1
make[1]: Leaving directory '/tmp/procps-ng-3.3.13'
make: *** [Makefile:1015: all] Error 2

Error 2 is (I believe) "No such file or directory", so something is missing.

worsel · 04-08-2018, 07:44 PM

The problem seems to be related to ncurses or ld. ls /lib64/libncur* gives:

Quote:

/lib64/libncurses.so.6 /lib64/libncursesw.so.6
/lib64/libncurses.so.6.1 /lib64/libncursesw.so.6.1

but procps-ng (actually ld) can't seem to find /lib64/libncursesw.so.6.

nobodino · 04-09-2018, 01:29 AM

Even if you do: ldconfig -v | grep libncursesw.so.6
you will see:
--------------
# ldconfig -v | grep libncursesw.so.6
ldconfig: Ne peut �valuer par stat /usr/x86_64-slackware-linux/lib64: Aucun fichier ou dossier de ce type
ldconfig: Chemin � /lib64 � donn� plus d'une fois
ldconfig: Ne peut �valuer par stat /libx32: Aucun fichier ou dossier de ce type
ldconfig: Chemin � /usr/lib64 � donn� plus d'une fois
ldconfig: Ne peut �valuer par stat /usr/libx32: Aucun fichier ou dossier de ce type
libncursesw.so.6 -> libncursesw.so.6.1
libncursesw.so.6 -> libncursesw.so.6.1
--------------
so it's there but not seen
and /etc/ld.so.conf is ok.