regression test up to "Thu Jan 9 21:57:44 UTC 2020": (x86_64 version)
- plasma-nm: fail
- libnm-qt: fail
- seamonkey: fail
- dconf: new fail, but the new dconf-0.35.1 builds like a charm, it may be the solution for this package. The dconf-editor builds fine with dconf-0.35.1.
---------------------
dconf-paths.c:(.text+0x230): multiple definition of `dconf_is_rel_path'; client/libdconf-client.a(dconf-paths.c.o):dconf-paths.c:(.text+0x230): first defined here
/usr/bin/ld: common/libdconf-common.a(dconf-paths.c.o): in function `dconf_is_rel_key':
dconf-paths.c:(.text+0x2e0): multiple definition of `dconf_is_rel_key'; client/libdconf-client.a(dconf-paths.c.o):dconf-paths.c:(.text+0x2e0): first defined here
/usr/bin/ld: common/libdconf-common.a(dconf-paths.c.o): in function `dconf_is_rel_dir':
dconf-paths.c:(.text+0x3a0): multiple definition of `dconf_is_rel_dir'; client/libdconf-client.a(dconf-paths.c.o):dconf-paths.c:(.text+0x3a0): first defined here
collect2: error: ld returned 1 exit status
[87/92] Compiling C object 'tests/59830eb@@engine@exe/engine.c.o'.
ninja: build stopped: subcommand failed.

1 members found this post helpful.

libplist doesn't buiild anymore:
-----------------------------
https://github.com/pypa/setuptools/issues/1458
about the steps that led to this unsupported combination.
************************************************************
sys.version_info < (3,) and warnings.warn("*" * 60 + msg + "*" * 60)
0.29.14. You should look at http://www.cython.org
checking for python2.7... (cached) /usr/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python2.7
checking for Python library path... -L/usr/lib64 -lpython2.7
checking for Python site-packages path... /usr/lib64/python2.7/site-packages
checking python extra libraries... -lpthread -ldl -lutil -lm
checking python extra linking flags... -Xlinker -export-dynamic
checking consistency of all components of python development environment... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libplist Cython bindings... Package libplist was not found in the pkg-config search path.
Perhaps you should add the directory containing `libplist.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libplist' found
Using built-in libplist Cython bindings (assuming this is a first build)
checking for supported compiler flags... -Wall -Wextra -Wredundant-decls -Wshadow -Wpointer-arith -Wwrite-strings -Wswitch-default -Wno-unused-parameter -Wno-strict-aliasing -fvisibility=hidden -pthread
checking whether make supports nested variables... (cached) yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libcnary/Makefile
config.status: creating src/Makefile
config.status: creating src/libplist.pc
config.status: creating src/libplist++.pc
config.status: creating include/Makefile
config.status: creating tools/Makefile
config.status: creating cython/Makefile
config.status: creating test/Makefile
config.status: creating fuzz/Makefile
config.status: creating doxygen.cfg
config.status: creating config.h
config.status: executing depfiles commands
config.status: error: in `/tmp/libplist-2.1.0':
config.status: error: Something went wrong bootstrapping makefile fragments
for automatic dependency tracking. Try re-running configure with the
'--disable-dependency-tracking' option to at least be able to build
the package (albeit without support for automatic dependency tracking).
See `config.log' for more details
-------------------------------

looking at the referenced github issue I think that a move to python-3.x maybe should be the thing to do in the long term, but in the meantime also an
before the configure block should do (as long that works).

1 members found this post helpful.

Thanks, the source tree has been updated and did the trick.
Only 3 packages remain not buildable for the time beeing:
- 2 kde4 packages: plasma-nm and libnm-qt (once plasma is integrated...)
- seamonkey: no patch available as far as I looked forward.

Nota:
-plasma has been nearly integrated in SFS, only deps packages need some patches to be built without failure (patches are available on the github project)
-the ada compiler has been integrated in the 'tools', so no need of "gnat-gpl-2017-x86_64-linux-bin.tar.gz" external package during rebuilding Slackware From Scratch.
-I found a trick to build libcaca without the external "jre-8u202-linux-x64.tar.gz" package by using the slackware14.2 package as for ksh93.

SFS can now be rebuilt without external packages, except during the "tools" building.