SBo scripts not building on current (read 1st post, pls)

Bouboulov · 03-24-2024, 05:20 PM

libiptcdata won't build on version 1.0.4 anymore.

I found an update on conraid's slackbuilds, it will build with 1.0.5.

kgha · 03-25-2024, 09:23 AM

Quote:

Originally Posted by Bouboulov

libiptcdata won't build on version 1.0.4 anymore.

Confirmed. Python2-related error:

Code:

checking for python... /usr/bin/python
checking for a version of Python >= '2.1.0'...   File "<string>", line 1
    import sys, string;                 ver = string.split(sys.version)[0];                 print ver >= '2.1.0'
                                                                                                  ^
SyntaxError: invalid syntax
no
configure: error: in `/tmp/SBo/libiptcdata-1.0.4':
configure: error:
This version of the AC_PYTHON_DEVEL macro
doesn't work properly with versions of Python before
2.1.0. You may need to re-run configure, setting the
variables PYTHON_CPPFLAGS, PYTHON_LDFLAGS, PYTHON_SITE_PKG,
PYTHON_EXTRA_LIBS and PYTHON_EXTRA_LDFLAGS by hand.
Moreover, to disable this check, set PYTHON_NOVERSIONCHECK
to something else than an empty string.

libiptcdata-1.0.5 source file here: https://github.com/ianw/libiptcdata/

EDIT: libiptcdata-1.0.4 builds if line 105 in buildscript is changed from

Code:

  ${py_option}-python

to

Code:

  ${py_option}-python3

USUARIONUEVO · 03-25-2024, 04:59 PM

Hi , nvidia-firmware fails.

Caused by python file , we have a old version with only support python2.

Fix updating the python file from the git repo to a newer version with support for python2 and python3.

You only need to upgrade the file --> extract_firmware.py

updated git file.
https://github.com/envytools/firmwar...ct_firmware.py

I tested on -current and works with python pointing to python3.

The seebang on the file is for "python" ... on 15.0 are python2 pointing and works, but on -current points to python3 and need the file updated to support python3.

Thanks!

As i say , no need touch nothing, only push an updated python file.

ponce · 03-26-2024, 11:55 AM

Quote:

Originally Posted by USUARIONUEVO

Hi , nvidia-firmware fails.

Caused by python file , we have a old version with only support python2.

Fix updating the python file from the git repo to a newer version with support for python2 and python3.

You only need to upgrade the file --> extract_firmware.py

updated git file.
https://github.com/envytools/firmwar...ct_firmware.py

I tested on -current and works with python pointing to python3.

The seebang on the file is for "python" ... on 15.0 are python2 pointing and works, but on -current points to python3 and need the file updated to support python3.

Thanks!

As i say , no need touch nothing, only push an updated python file.

unfortunately looks like the maintainer of the nvidia-firmware script abandoned all of its scripts, this specifically hadn't been updated in 6 years: you could write to him to take care of this or you could step in as a maintainer but, I'm sorry, I won't touch this neither with a long pole.

USUARIONUEVO · 03-26-2024, 12:56 PM

Quote:

Originally Posted by ponce

unfortunately looks like the maintainer of the nvidia-firmware script abandoned all of its scripts, this specifically hadn't been updated in 6 years: you could write to him to take care of this or you could step in as a maintainer but, I'm sorry, I won't touch this neither with a long pole.

Thanks! , you make me laungh.

No mantainer ,but contact the mantainer ..hahaha.

In the case he contact me, can say do nothing , cause 15.0 no have problems.

Is a -current problem.

ponce · 03-26-2024, 02:56 PM

Quote:

Originally Posted by USUARIONUEVO

Thanks! , you make me laungh.

No mantainer ,but contact the mantainer ..hahaha.

In the case he contact me, can say do nothing , cause 15.0 no have problems.

Is a -current problem.

ok, so as it doesn't have a maintainer and nobody seems interested (you too) I'll remove it from the current repository (I won't maintain myself abandoned and non-working scripts, I hope you understand).

rherbert · 03-26-2024, 04:40 PM

Attempting to build libpst on -current (latest) results in the following:

Code:

make[2]: Entering directory '/tmp/SBo/libpst-0.6.76/python'
/bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -I./../src  -I/usr/include/python2.7    -O2 -fPIC -MT python-libpst.lo -MD -MP -MF .deps/python-libpst.Tpo -c -o python-libpst.lo python-libpst.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -I./../src -I/usr/include/python2.7 -O2 -fPIC -MT python-libpst.lo -MD -MP -MF .deps/python-libpst.Tpo -c python-libpst.cpp  -fPIC -DPIC -o .libs/python-libpst.o
mv -f .deps/python-libpst.Tpo .deps/python-libpst.Plo
/bin/sh ../libtool  --tag=CXX   --mode=link g++  -O2 -fPIC -module  -avoid-version  -o _libpst.la -rpath /usr/lib64/python2.7/site-packages python-libpst.lo -l ../src/libpst.la 
libtool: link: g++  -fPIC -DPIC -shared -nostdlib /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/crtbeginS.o  .libs/python-libpst.o   -Wl,-rpath -Wl,/tmp/SBo/libpst-0.6.76/src/.libs -l ../src/.libs/libpst.so -lz -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0 -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/crtendS.o /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64/crtn.o  -O2   -Wl,-soname -Wl,_libpst.so -o .libs/_libpst.so
/usr/bin/ld: cannot find -l../src/.libs/libpst.so: No such file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:501: _libpst.la] Error 1
make[2]: Leaving directory '/tmp/SBo/libpst-0.6.76/python'
make[1]: *** [Makefile:576: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libpst-0.6.76'
make: *** [Makefile:462: all] Error 2

The file /tmp/SBo/libpst-0.6.76/.libs/libpst.so is present as a symlink, and points to libpst.so.4.1.18 in the same directory.

There's code in the SlackBuild meant to ignore Python2 if it isn't present. Perhaps it's detecting an incomplete installation of Python2?

I don't have need for libpst, as I've been retired for over two years and no longer have any need to import a PST file, but I just wanted to raise a flag.

Thanks.

ponce · 03-26-2024, 04:57 PM

Quote:

Originally Posted by rherbert

Attempting to build libpst on -current (latest) results in the following:

Code:

make[2]: Entering directory '/tmp/SBo/libpst-0.6.76/python'
/bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -I./../src  -I/usr/include/python2.7    -O2 -fPIC -MT python-libpst.lo -MD -MP -MF .deps/python-libpst.Tpo -c -o python-libpst.lo python-libpst.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I./.. -I./../src -I/usr/include/python2.7 -O2 -fPIC -MT python-libpst.lo -MD -MP -MF .deps/python-libpst.Tpo -c python-libpst.cpp  -fPIC -DPIC -o .libs/python-libpst.o
mv -f .deps/python-libpst.Tpo .deps/python-libpst.Plo
/bin/sh ../libtool  --tag=CXX   --mode=link g++  -O2 -fPIC -module  -avoid-version  -o _libpst.la -rpath /usr/lib64/python2.7/site-packages python-libpst.lo -l ../src/libpst.la 
libtool: link: g++  -fPIC -DPIC -shared -nostdlib /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/crtbeginS.o  .libs/python-libpst.o   -Wl,-rpath -Wl,/tmp/SBo/libpst-0.6.76/src/.libs -l ../src/.libs/libpst.so -lz -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0 -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/crtendS.o /usr/lib64/gcc/x86_64-slackware-linux/13.2.0/../../../../lib64/crtn.o  -O2   -Wl,-soname -Wl,_libpst.so -o .libs/_libpst.so
/usr/bin/ld: cannot find -l../src/.libs/libpst.so: No such file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:501: _libpst.la] Error 1
make[2]: Leaving directory '/tmp/SBo/libpst-0.6.76/python'
make[1]: *** [Makefile:576: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libpst-0.6.76'
make: *** [Makefile:462: all] Error 2

The file /tmp/SBo/libpst-0.6.76/.libs/libpst.so is present as a symlink, and points to libpst.so.4.1.18 in the same directory.

There's code in the SlackBuild meant to ignore Python2 if it isn't present. Perhaps it's detecting an incomplete installation of Python2?

I don't have need for libpst, as I've been retired for over two years and no longer have any need to import a PST file, but I just wanted to raise a flag.

Thanks.

just delete these lines from the SlackBuild and you should be good to go

Code:

--- ./libpst.SlackBuild.orig    2024-03-23 15:52:42.265158000 +0100
+++ ./libpst.SlackBuild 2024-03-26 22:54:42.286158000 +0100
@@ -128,29 +128,8 @@
 # first build). autotools doesn't make it easy or even necessarily
 # possible to build only part of a project :(
 
-# Python 2 build. If python2 ever really does go away, this code will
-# silently omit python2 support from the package.
-if type -p python2 &>/dev/null; then
-  PY2VER="$( python2 --version 2>&1 | cut -d' ' -f2 | cut -d. -f1,2 )"
-
-  # ./configure --help claims that I can set PYTHON_VERSION in the environment
-  # and it'll use that, but it doesn't work. So I have to use this abomination:
-  sed -i.bak 's,\<python3\..\>,python'$PY2VER',g' m4/ax_python.m4
-
-  buildit
-
-  mv $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER $PKG/.keep.python2
-  rm -rf $PKG/*
-
-  # put everything back the way it was.
-  make distclean
-  mv m4/ax_python.m4.bak m4/ax_python.m4
-fi
-
 # Python 3 build
 buildit
-[ -e $PKG/.keep.python2 ] && \
-  mv $PKG/.keep.python2 $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER
 
 gzip -9 $PKG/usr/man/man?/*.?

rherbert · 03-26-2024, 05:11 PM

Quote:

Originally Posted by ponce

just delete these lines from the SlackBuild and you should be good to go

Code:

--- ./libpst.SlackBuild.orig    2024-03-23 15:52:42.265158000 +0100
+++ ./libpst.SlackBuild 2024-03-26 22:54:42.286158000 +0100
@@ -128,29 +128,8 @@
 # first build). autotools doesn't make it easy or even necessarily
 # possible to build only part of a project :(
 
-# Python 2 build. If python2 ever really does go away, this code will
-# silently omit python2 support from the package.
-if type -p python2 &>/dev/null; then
-  PY2VER="$( python2 --version 2>&1 | cut -d' ' -f2 | cut -d. -f1,2 )"
-
-  # ./configure --help claims that I can set PYTHON_VERSION in the environment
-  # and it'll use that, but it doesn't work. So I have to use this abomination:
-  sed -i.bak 's,\<python3\..\>,python'$PY2VER',g' m4/ax_python.m4
-
-  buildit
-
-  mv $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER $PKG/.keep.python2
-  rm -rf $PKG/*
-
-  # put everything back the way it was.
-  make distclean
-  mv m4/ax_python.m4.bak m4/ax_python.m4
-fi
-
 # Python 3 build
 buildit
-[ -e $PKG/.keep.python2 ] && \
-  mv $PKG/.keep.python2 $PKG/usr/lib$LIBDIRSUFFIX/python$PY2VER
 
 gzip -9 $PKG/usr/man/man?/*.?

Thanks! That did the trick. Hopefully, this will help someone else.

titopoquito · 03-29-2024, 06:20 AM

puddletag needs two patches because of recent changes to pyparsing. The issue will be solved when pyparsing will have got an update to 3.1.3 from what I've read.

Source: https://github.com/puddletag/puddletag/issues/884
The puddletag pull request that would resolve the issue: https://github.com/puddletag/puddletag/pull/880

And the two patches supplied there that need to be applied:
https://github.com/puddletag/puddlet...ba94d8e24982f0
https://github.com/puddletag/puddlet...ae441d9f1ebc64

Without the patches puddletag compiled but would throw an error (when started from command line) and deny to start. It starts with only the first patch applied, but I have not tested if I would get an error on any tagging operation.

USUARIONUEVO · 03-30-2024, 09:27 AM

Hi , wxPython4 fails to build.

Cython up to branch 3 offends wxPython

The github issue
https://github.com/wxWidgets/Phoenix/issues/2514

There is a patch
https://github.com/wxWidgets/Phoenix...e6d0b53c115378

If some one need to build wxPython , first remove Cython , build wxPython4 ..and reinstall Cython.

There is a direct patch from gentoo
http://mirror.sbb.rs/gentoo-portage/...cython-3.patch

EDIT: Patch tested , works perfectly , now build with cython-3.x

The patch is supossed to apply for next release , for now the easy way is apply the single patch , instead grab a git tarball.

Thanks!

USUARIONUEVO · 03-30-2024, 09:58 AM

Hi again , cryptography and other python stuff , fails to build cause have direct export to old 3.9 directory

Quote:

export PYTHONPATH=/opt/python3.9/site-packages/

I contact the mantainer and proposed to use the command to get dinamically the python3 branch , we need wait to fixes.

Some modules are from willy and others from fourtysixandtwo , be patient.

for now i found this affected by python3 upgrade.

Quote:

python3-setuptools-rust-opt
cryptography
python3-bcrypt

One is fixed now
https://git.slackbuilds.org/slackbui...267804db6c7780

Daedra · 03-30-2024, 11:53 AM

python-colour is failing on -current after the python-3.11 upgrade. I maintain this package since it is a dependency of Polychromatic. I am working on it, but if anyone wants to tag in or has any ideas on how to fix please let me know.

Code:

Building package for python-colour...
colour-0.1.5/.package
Missing version information: running './autogen.sh'...
/usr/lib/python3.11/site-packages/setuptools/dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!

        ********************************************************************************
        Usage of dash-separated 'description-file' will not be supported in future
        versions. Please use the underscore name 'description_file' instead.

        By 2024-Sep-26, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  opt = self.warn_dash_deprecation(opt, section)
/usr/lib/python3.11/site-packages/setuptools/dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!

        ********************************************************************************
        Usage of dash-separated 'requires-dist' will not be supported in future
        versions. Please use the underscore name 'requires_dist' instead.

        By 2024-Sep-26, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
        ********************************************************************************

!!
  opt = self.warn_dash_deprecation(opt, section)
/usr/lib/python3.11/site-packages/setuptools/__init__.py:81: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  dist.fetch_build_eggs(dist.setup_requires)
Traceback (most recent call last):
  File "/tmp/SBo/colour-0.1.5/setup.py", line 61, in <module>
    setup(
  File "/usr/lib/python3.11/site-packages/setuptools/__init__.py", line 104, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 147, in setup
    _setup_distribution = dist = klass(attrs)
                                 ^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 307, in __init__
    _Distribution.__init__(self, dist_attrs)
  File "/usr/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 283, in __init__
    self.finalize_options()
  File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 658, in finalize_options
    ep(self)
  File "/usr/lib/python3.11/site-packages/setuptools/dist.py", line 678, in _finalize_setup_keywords
    ep.load()(self, ep.name, value)
  File "/usr/lib/python3.11/site-packages/d2to1/core.py", line 30, in d2to1
    from setuptools.dist import _get_unpatched
ImportError: cannot import name '_get_unpatched' from 'setuptools.dist' (/usr/lib/python3.11/site-packages/setuptools/dist.py)

USUARIONUEVO · 03-30-2024, 01:23 PM

@Daedra

first of all ...ensure your build for python2 using direct call "python2 setup.py" ..cause -current have python pointing to python3.

second thing ... i can build you package using the wheel file instead the sources.

for python3

Quote:

# build python3
pip3 install --isolated --root=$PKG --ignore-installed --no-deps *.whl

Using the wheel installer ...
https://pypi.org/project/colour/#files

gian_d · 03-30-2024, 01:35 PM

The slackbuild of packages in subject (and surely even other packages) need a little fix for current because refer to /usr/lib64python3.9

For python3-pythran:

Code:

# Remove bundled boost and xsimd
rm -r $PKG/usr/lib*/python*/site-packages/pythran/{boost,xsimd}

instead of

Code:

# Remove bundled boost and xsimd
rm -r $PKG/usr/lib${LIBDIRSUFFIX}/python*/site-packages/pythran/{boost,xsimd}

(this should works also for Slackware 15.0)

For python3-twisted a fix is needed I think for -current only. I don't know if sed can accept wildcard characters, I solved as following:

Code:

# Fix initialization bug with zope.interface 6+
sed -i 's#zope-interface#zope.interface#' "$PKG/usr/lib/python3.11/site-packages/twisted-${VERSION}.dist-info/METADATA"

instead of

Code:

# Fix initialization bug with zope.interface 6+
sed -i 's#zope-interface#zope.interface#' "$PKG/usr/lib${LIBDIRSUFFIX}/python3.9/site-packages/twisted-${VERSION}.dist-info/METADATA"

This fix should work also in -current 32bit since the default path was /usr/lib even before the upgrade to python3.11