SBo scripts not building on current (read 1st post, pls)
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i newer use kernel patching, only new clear compilation and reboot. i know what is this impossible for must users.
And on rare occasions I use it to medical treat my system.
For compilation Libreoffice-7, i'm use apache-ant from http://sbopkg.org "sbopkg -V ?" (select current)
Other pkg's (i.e java-jdk-14.0.1), i use from brand sites.
Code:
Also today i install apache-ant, first use SBo, compilation libreoffice-7.0.1.2 finish at this:
" ... checking whether Ant is >= 1.6.0... yes, 1.9.14
checking for JUnit 4... configure: error: cannot find JUnit 4 jar; please install one in the default location (/usr/share/java),
specify its pathname via --with-junit=..., or disable it via --without-junit"
I don't warry but i install my lovely chromium-bsu, warzone2100 and much more.
Today i was in ubuntustudio.org 20.10 testing state with latest newest applications.
And you know what i think ? XFCE is much preffered opposite KDE PLASMA 5.19.5.
For compilation Libreoffice-7, i'm use apache-ant from http://sbopkg.org "sbopkg -V ?" (select current)
Other pkg's (i.e java-jdk-14.0.1), i use from brand sites.
Code:
Also today i install apache-ant, first use SBo, compilation libreoffice-7.0.1.2 finish at this:
" ... checking whether Ant is >= 1.6.0... yes, 1.9.14
checking for JUnit 4... configure: error: cannot find JUnit 4 jar; please install one in the default location (/usr/share/java),
specify its pathname via --with-junit=..., or disable it via --without-junit"
hi Roman,
remember that you should read the README of every SlackBuild you build from this repository: I quote the one from LibreOffice here
Code:
3. Previously, a number of Java Development Kits have been suitable for building
LibreOffice. At the moment however (since, at least, LO version 7.0.0.3) this
build has been tested only with jdk11 - this is now the default. If the jdk11
prerequisite is not acceptable for some reason, it is still possible to build
LibreOffice (with somewhat reduced capability in LO Base) by running:
JAVA=no sh LibreOffice.SlackBuild
note also that we don't have any 7.0.1.2 version in this repository: if you are using another SlackBuild instead of the one in this repository this topic is not the place to discuss it (read the first post).
hi Roman,
remember that you should read the README of every SlackBuild you build from ...
JUnit is *.jar JAVA application.jar .
Code:
./configure -- JAVA_HOME=/usr/java/jdk-14.0.1
Or other newest JAVA, for ALL app's, who mean like a WINE, and other who use JAVA..
Or other newest version for testing with Slackware64/current.
Now LibreOffice.org 7.0.1.2 .
What to say some one else other ?
Last edited by Roman Dyaba; 09-29-2020 at 11:50 PM.
spice-gtk is failing with the following error message:
Code:
Traceback (most recent call last):
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 5, in <module>
from gtkdoc_uninstalled import builddir
ModuleNotFoundError: No module named 'gtkdoc_uninstalled'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/gtkdoc-rebase", line 32, in <module>
from gtkdoc import common, config, rebase
File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 29, in <module>
from . import config
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 8, in <module>
from gtkdoc.config_data import *
ModuleNotFoundError: No module named 'gtkdoc.config_data'
spice-gtk is failing with the following error message:
Code:
Traceback (most recent call last):
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 5, in <module>
from gtkdoc_uninstalled import builddir
ModuleNotFoundError: No module named 'gtkdoc_uninstalled'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/gtkdoc-rebase", line 32, in <module>
from gtkdoc import common, config, rebase
File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 29, in <module>
from . import config
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 8, in <module>
from gtkdoc.config_data import *
ModuleNotFoundError: No module named 'gtkdoc.config_data'
remember that you have to carefully read the current's ChangeLog for additional steps to take during updates: have you already reinstalled linuxdoc-tools as indicated there?
Code:
Tue Sep 15 18:51:00 UTC 2020
[...]
l/glib2-2.66.0-x86_64-2.txz: Rebuilt.
Build against system gtk-doc and don't bundle a newer version. You'll need
to reinstall the linuxdoc-tools package to restore the correct version of
gtk-doc. Thanks to chrisVV.
arpack-ng package fails to build on -current due to failure in one of the tests (icb_arpack_cpp).
This was reported upstream and allegedly fixed with some patches in fedora.
I thought I needed this to build FreeFem, since it's reported as a dependency on SBo, but it turns out that FreeFem builds
happily without it, maybe it should be flagged as optional.
arpack-ng package fails to build on -current due to failure in one of the tests (icb_arpack_cpp).
This was reported upstream and allegedly fixed with some patches in fedora.
I've just tried to build it and compilation went fine with the gcc suite we have in current: have you by any chance tried to build this with the gcc 10.x in /testing? that is not yet supported by this repository and will be when it will get out of /testing and into current in place of 9.x.
Quote:
Originally Posted by giomat
I thought I needed this to build FreeFem, since it's reported as a dependency on SBo, but it turns out that FreeFem builds
happily without it, maybe it should be flagged as optional.
which dependencies are optional or not is actually decided by the maintainer: he decides which features are mandatory for the intended use of the application.
you can ask him if it's ok to have those features optional or add a note into the README about them, but in the end it's his call.
fvwm3 canot be built. There's an error with go lang:
Code:
CCLD FvwmMFL
make[3]: Leaving directory '/tmp/SBo/fvwm3-1.0.1/modules/FvwmMFL'
make[3]: Entering directory '/tmp/SBo/fvwm3-1.0.1/modules'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/tmp/SBo/fvwm3-1.0.1/modules'
make[2]: Leaving directory '/tmp/SBo/fvwm3-1.0.1/modules'
Making all in bin
make[2]: Entering directory '/tmp/SBo/fvwm3-1.0.1/bin'
Making all in FvwmPrompt
make[3]: Entering directory '/tmp/SBo/fvwm3-1.0.1/bin/FvwmPrompt'
go build -mod=vendor -o FvwmPrompt -v
go: inconsistent vendoring in /tmp/SBo/fvwm3-1.0.1/bin/FvwmPrompt:
github.com/abiosoft/ishell@v2.0.0+incompatible: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/abiosoft/readline@v0.0.0-20180607040430-155bce2042db: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/chzyer/logex@v1.1.10: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/chzyer/test@v0.0.0-20180213035817-a1ea475d72b1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/fatih/color@v1.9.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/flynn-archive/go-shlex@v0.0.0-20150515145356-3f9db97f8568: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/mattn/go-isatty@v0.0.12: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/sirupsen/logrus@v1.6.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/stretchr/testify@v1.6.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
golang.org/x/sys@v0.0.0-20200212091648-12a6c2dcc1e4: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
run 'go mod vendor' to sync, or use -mod=mod or -mod=readonly to ignore the vendor directory
make[3]: *** [Makefile:539: build] Error 1
make[3]: Leaving directory '/tmp/SBo/fvwm3-1.0.1/bin/FvwmPrompt'
make[2]: *** [Makefile:737: all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/fvwm3-1.0.1/bin'
make[1]: *** [Makefile:510: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/fvwm3-1.0.1'
make: *** [Makefile:451: all] Error 2
fvwm3 canot be built. There's an error with go lang:
before testing it here, had you logout and logged in again in your root session after having installed google-go-lang and tried to build fvwm3?
you should do it to source the file in /etc/profile.d, like explained in its README.
before testing it here, had you logout and logged in again in your root session after having installed google-go-lang and tried to build fvwm3?
you should do it to source the file in /etc/profile.d, like explained in its README.
EDIT: I can confirm it builds fine here.
I had google-go-lang already installed previously, and I logged in and out of root many times so the profile.d files were sourced several times afterwards but the installation still failed.
I even tried to set again the GOPATH env variable, and still failed.
I usually build SlackBuilds as root via su, so I thought I should build this package as console root.
I tried rebuilding google-go-lang first and then building fvwm3 from a console root session and it worked. Funny. Thanks for the tips.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.