[SOLVED] Solaar slackbuilds package installs libraries in /lib/

RandomTroll · 04-25-2024, 09:22 PM

But other Python packages install in /usr/lib64. I had to move Solaar's to get it to run.

business_kid · 04-26-2024, 06:27 AM

Where is set in the initial Slackbuild for libs? Does it pass --with-libdir=/usr/lib64?

RandomTroll · 04-27-2024, 02:05 PM

Quote:

Originally Posted by business_kid

Where is set in the initial Slackbuild for libs? Does it pass --with-libdir=/usr/lib64?

I can't see one. Is this my fault? Should I have set something?

BrunoLafleur · 04-27-2024, 03:32 PM

You could change the Slackbuild as :

Add under OUTPUT=${OUTPUT:-/tmp} line :

if [ "$ARCH" = "i586" ]; then
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
LIBDIRSUFFIX="64"
else
LIBDIRSUFFIX=""
fi

Replace :

python3 setup.py install

With :

PYVER=$(python3 --version | cut -d' ' -f2|cut -d'.' -f1-2)
python3 setup.py install --root=$PKG --install-platlib=/usr/lib$LIBDIRSUFFIX/python${PYVER}/site-packages

fourtysixandtwo · 04-27-2024, 06:37 PM

RandomTroll, are you running slackware64-current then? This is a bug that should be reported upstream(already has https://github.com/pwr-Solaar/Solaar/issues/2454). It is normal with the upgrade to python 3.11 that they can be installed to /usr/lib or /usr/lib64, setuptools will decide.

If I was to guess, Solaar is not honoring the python search path for some reason. This is indeed a problem with Solaar. Everything else I've tested so far has no problems with this. -this is wrong, see next post

Code:

# python3 -c "import sys; print('\n'.join(sys.path))"

/usr/lib64/python311.zip
/usr/lib64/python3.11
/usr/lib64/python3.11/lib-dynload
/usr/lib64/python3.11/site-packages
/usr/lib/python3.11/site-packages

# python3 -c "import solaar as i; print(i.__file__,i.__version__)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'solaar'

Edit: I also tried upgrading to Solaar-1.1.12 which was just released over an hour ago but the problem remains.

fourtysixandtwo · 04-27-2024, 08:30 PM

BrunoLafleur's fix doesn't work either and neither of us looked far enough down in the slackbuild. The confusing part was that this wasn't an issue on 15.0, but due to to difference I mentioned in the previous post about the upgrade to 3.11.

This is the fix that's needed to the SlackBuild and will work with 15.0 as well. I've contacted the maintainer.

Code:

diff --git a/system/Solaar/Solaar.SlackBuild b/system/Solaar/Solaar.SlackBuild
index e7d07704..95a46432 100644
--- a/system/Solaar/Solaar.SlackBuild
+++ b/system/Solaar/Solaar.SlackBuild
@@ -68,7 +68,8 @@ find -L . \
 
 python3 setup.py install --root=$PKG
 
+mkdir $PKG/lib
-mv $PKG/usr/lib $PKG/
+mv $PKG/usr/lib/udev $PKG/lib/
 sed -i 's/#MODE="0660", GROUP="plugdev"/MODE="0660", GROUP="plugdev"/g' $PKG/lib/udev/rules.d/42-logitech-unify-permissions.rules
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION

RandomTroll · 05-01-2024, 12:08 AM

Quote:

Originally Posted by fourtysixandtwo

RandomTroll, are you running slackware64-current then? This is a bug that should be reported upstream(already has https://github.com/pwr-Solaar/Solaar/issues/2454).

I'm ArthurPeabody.

Quote:

Originally Posted by fourtysixandtwo

This is the fix that's needed to the SlackBuild and will work with 15.0 as well. I've contacted the maintainer.

Thanks.

fourtysixandtwo · 05-01-2024, 12:51 AM

I figured it might be.

Fix will be included in this weeks updates.

https://git.slackbuilds.org/slackbui...b971abe9958214