[Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does not compile with opencv 3.4.1

Matteo Bernardini matteo.bernardini at gmail.com
Wed Mar 14 19:51:34 UTC 2018

2018-03-14 14:41 GMT+01:00 Ythogtha <yth at ythogtha.org>:
>         Anyway, I found the problem.
> It's with the opencv.SlackBuild, or more precisely with opencv itself because
> the SlackBuild didn't change and was working fine before.
> OpenCV libraries are installed in /usr/lib6464/ !
> In the opencv.SlackBuild there is a LIBDIRSUFFIX="64" configured when ARCH=x86_64
> and it seems the opencv make process now does that step itself, installing
> itself into /usr/lib64, so adding the LIBDIRSUFFIX="64" moves the .so files
> into /usr/lib6464/
>         So setting LIBDIRSUFFIX="" looks like a good idea.
> Except then there are python libraries installed in /usr/lib/ !
> usr/lib/python2.7/site-packages/cv2.so
> usr/lib/python3.6/site-packages/cv2.cpython-36m-x86_64-linux-gnu.so
> And import cv2 doesn't work in either python or python3.
>         I tried moving usr/lib/python* into usr/lib64/ just before makepkg in the
> SlackBuild, and everything seems to work fine, I can import cv2 in python and
> python3. The hack is ugly and there should be a cleaner way to handle that.

IMHO the best solution for that is to modify a little more the patch
used by the SlackBuild: I attach the new version

-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch_fsh-3.4.1.diff
Type: text/x-patch
Size: 1930 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180314/2cd4a1f3/attachment.bin>

More information about the SlackBuilds-users mailing list