SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 742
Rep:
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.
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 742
Rep:
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
-------------------------------
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
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 742
Rep:
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.
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 742
Rep:
I installed binutils-2.34 and glibc-2.31 and gcc doesn't build on Slackware64-current with these two new packages.
------------------------------
usr" "infodir=/usr/info" "libdir=/usr/lib64" "includedir=/usr/include" "prefix=/usr" "tooldir=/usr/x86_64-slackware-linux" "gdc_include_dir=/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/include/d" "AR=ar" "AS=/tmp/gcc-9.2.0/gcc.build.lnx/./gcc/as" "LD=/tmp/gcc-9.2.0/gcc.build.lnx/./gcc/collect-ld" "RANLIB=ranlib" "NM=/tmp/gcc-9.2.0/gcc.build.lnx/./gcc/nm" "NM_FOR_BUILD=" "NM_FOR_TARGET=nm" "DESTDIR=" "WERROR=" DO=all multi-do # make
make[4]*: on quitte le répertoire «*/tmp/gcc-9.2.0/gcc.build.lnx/x86_64-slackware-linux/libphobos*»
make[3]*: on quitte le répertoire «*/tmp/gcc-9.2.0/gcc.build.lnx/x86_64-slackware-linux/libphobos*»
make[2]*: on quitte le répertoire «*/tmp/gcc-9.2.0/gcc.build.lnx/x86_64-slackware-linux/libphobos*»
make[1]*: on quitte le répertoire «*/tmp/gcc-9.2.0/gcc.build.lnx*»
make: *** [Makefile:25892: bootstrap] Error 2
rm: impossible de supprimer '/tmp/tmp-la-file': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/*++*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/include/c++': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/*++*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/cc1plus': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/man/man1/*++*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/share/gdb': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/share/gcc-9.2.0/python/libstdcxx': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/*gfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/*95*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/*77*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/info/gfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/libgfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/finclude': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/libgfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/f951': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/libgfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/man/man1/gfortran*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/gnat*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/gpr*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/info/gnat*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/gnat1': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/adainclude': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/adalib': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/libobjc*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/cc1obj': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/cc1objplus': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/include/objc': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/gcc/x86_64-slackware-linux/9.2.0/include/cc1objplus': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/*gccgo*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/go': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/bin/gofmt': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/cgo': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/libexec/gcc/x86_64-slackware-linux/9.2.0/go1': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/info/gccgo.info.gz': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/go': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/libgo.so*': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/libgobegin.a': Aucun fichier ou dossier de ce type
mv: impossible d'évaluer '/tmp/package-gcc/usr/lib64/libgolibbegin.a': Aucun fichier ou dossier de ce type
-----------------------------------------------------------
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 742
Rep:
Your piece of advice works for gcc by adding this line to the gcc.Slackbuild allows gcc to build till the end.
--------------------------------
# fix a problem introduced by glibc-2.31
sed -e '1161 s|^|//|' -i libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
--------------------------------
the same line allows to build the tools and build1_s.list without problem.
I'll go on building the rest of SFS from now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.