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'm sorry but I don't know when I will have the time needed to fix all of the python messes so consider them broken for the time being.
Im reporting solutions ... apparently upgrade versions , fix issues.
we need update version for pytz and numpy ... after this python3-matplotlib no need nothing , builds fine.
I build large number of python3 modules ,, all builds fine ,except this two mentiones , pytz and numpy3 , upgrade versions , and all works again.
EDIT: willy update pytz ...probably now working on numpy3 , thanks all for this thread , is great when all work in same direction to make easy for other users.
On libtorrent-rasterbar, you might want to try using cmake. I switched to a cmake build last year with no ussues. I upgraded to 1.2.14 yesterday.
I fixed it by downloading slackware update and manually reinstalling packages in l and d directories.
Not sure what happened with slackpkg but using "slackpkg reinstall d l" did not fix it. I ran "slackpkg install-new" so it was not it either.
Hi , after numpy3 update , python3-matplotlib builds , but not work properly.
when some app try import python3-matplotlib
Quote:
import matplotlib.pyplot as plt
File "/usr/lib64/python3.10/site-packages/matplotlib/__init__.py", line 107, in <module>
from collections import MutableMapping
ImportError: cannot import name 'MutableMapping' from 'collections' (/usr/lib64/python3.10/collections/__init__.py)
I rebuild 2 times to ensure , ever same error
we need upgrade --> matplotlib-3.4.3 --> all fine
Thanks!
EDIT: In order to build the new version , need comment this line
Quote:
cat "${CWD}/setupext.py" > setupext.py
Last edited by USUARIONUEVO; 10-10-2021 at 06:01 AM.
Like I've said before I don't use SBo for my builds. That said, regarding enblend-enfuse. If any one is interested. I am able to build it using cmake. Unfortunately the 4.2 version does not build with cmake (CMake Errors). The latest commit from the mercurial that can be built with exiv2 is acca56. Attempting to build a later commit results in "Found exiv2 library, but this library is not recent enough to compile". Kind of crazy to require a version of exiv2 that has not been release yet. Building the latest version "default" (commit b23637) results in the errors pointed out by metageek.
This is what I am using for the build. The NAMDIR variable is needed to get the manpages in the right place for Slackware The ENABLE_METADATA_TRANSFER variable is needed to build with exiv2.
Code:
export MANDIR=/usr/man
mkdir -p build
cd build
cmake .. \
-DCMAKE_C_FLAGS_RELEASE="$SLKCFLAGS" \
-DCMAKE_CXX_FLAGS_RELEASE="$SLKCFLAGS" \
-DCMAKE_INSTALL_PREFIX=/usr \
-DBUILD_SHARED_LIBS=on \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_OPENMP=on \
-DENABLE_METADATA_TRANSFER=on \
-Wno-dev \
make $NUMJOBS
make install DESTDIR=$PKGDIR
cd -
Interesting to note that my last 4.2 build did not have exiv2 support. I don't believe the SBo builds with it either based on that I was using the same build parameters as the SBo build with the exception of an added --enable-openmp option.
Code:
./enblend --show-software-components
Compiler
g++ 10.3.0
implementing OpenMP standard of 2015-11
Libraries
GSL: 2.6
Little CMS: 2.12.0
Vigra: 1.11.1
My current build 20191021_acca56-1 does include exiv2.
Code:
enblend --show-software-components
Compiler
g++ 11.2.0
implementing OpenMP standard of 2015-11
Libraries
Exif2: 0.27.4
GSL: 2.7
Little CMS: 2.12.0
Vigra: 1.11.1
Last edited by chrisretusn; 10-10-2021 at 07:45 AM.
Not problems to build , and mantains boot python2 and python3 support , but i think , the correct way , is start split this style of slackbuilds , because mantainer of python modules can stop supporting python2 , and then we are ready to go in to separate slackbuilds.
I know , this is a BIG , VERY BIG work to do , but start now , whit the broken detected is more easy.
Not problems to build , and mantains boot python2 and python3 support , but i think , the correct way , is start split this style of slackbuilds , because mantainer of python modules can stop supporting python2 , and then we are ready to go in to separate slackbuilds.
I know , this is a BIG , VERY BIG work to do , but start now , whit the broken detected is more easy.
Thanks for all the support.
Thanks, ran just into this same problem on my way to recompiling inkscape. And I agree. I do not really understand why for current, when python3 is/should be the standard (some) scripts still need to cater for python2 at all. Why do we need to build these python bits twice when one will be needed/used? For people that still need python2, separate build-scripts could be put in place; they possibly need outdated versions of these modules/programs to get these compiled. For most python3 stuff we need latest versions due to the upgrade of python3 itself...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.