From: terrible apps <horribleapps@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: Re: upgrade to opencv4.2.0 via xbps-src
Date: Mon, 20 Jan 2020 14:52:32 -0800 (PST) [thread overview]
Message-ID: <44f5762a-ab9b-4014-8cb0-0df7fc0a9f16@googlegroups.com> (raw)
In-Reply-To: <9f1e2314-ee33-4ded-b77f-106cfdb072b5@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2684 bytes --]
Got it!
needed to change
vmove usr/share/OpenCV to vmove usr/share/opencv4
Now got this error:
SONAME: libopencv_ml.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_photo.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_dnn.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_highgui.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_objdetect.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_stitching.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_video.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_videoio.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_imgcodecs.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_calib3d.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_features2d.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_flann.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_imgproc.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libopencv_core.so.4.2 <-> UNKNOWN PKG PLEASE FIX!
SONAME: libstdc++.so.6 <-> libstdc++>=4.4.0_1
SONAME: libm.so.6 <-> glibc>=2.29_1
SONAME: libgcc_s.so.1 <-> libgcc>=4.4.0_1
SONAME: libc.so.6 <-> glibc>=2.29_1
=> ERROR: libopencv-python3-4.2.0_4: cannot guess required shlibs, aborting!
Trying to figure this error out now.
On Monday, January 20, 2020 at 12:24:23 AM UTC-8, terrible apps wrote:
>
> I am trying to update the template in opencv for xbps-src. I learning
> linux and would like to help with development to help me learn better.
>
> I am trying to upgrade it to opencv4.2.0.
>
> I am running into the following error:
> mv: cannot stat '/destdir//opencv-4.2.0/usr/share/OpenCV': No such file or
> directory
> => ERROR: libopencv-devel-4.2.0_4: pkg_install: 'mv ${_destdir}/$files
> ${_pkgdestdir}/${_targetdir}' exited with 1
> => ERROR: in _vmove() at common/environment/setup/install.sh:232
> => ERROR: in _noglob_helper() at common/environment/setup/install.sh:12
> => ERROR: in pkg_install() at srcpkgs/libopencv-devel/template:49
>
> I had added the following flag: DOPENCV_GENERATE_PKGCONFIG=ON
> that seemed to help remove a previous error. I don't know if the error is
> on the void linux end or opencv end.
>
> Would appreciate help! I posted my question on voidlinux chat but didn't
> get a reply before leaving the chat.
> Thanks,
>
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/44f5762a-ab9b-4014-8cb0-0df7fc0a9f16%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3631 bytes --]
next prev parent reply other threads:[~2020-01-20 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 8:24 terrible apps
2020-01-20 22:52 ` terrible apps [this message]
2020-01-22 23:29 ` Andrew Benson
2020-01-23 8:42 ` terrible apps
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44f5762a-ab9b-4014-8cb0-0df7fc0a9f16@googlegroups.com \
--to=horribleapps@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).