On Mon, 5 Oct 2020 at 07:59, Pavel Raiskup <praiskup@xxxxxxxxxx> wrote: > > On Sunday, October 4, 2020 7:44:49 PM CEST Iñaki Ucar wrote: > > On Sun, 4 Oct 2020 at 18:39, Jerry James <loganjerry@xxxxxxxxx> wrote: > > > > > > On Sun, Oct 4, 2020 at 7:07 AM Iñaki Ucar <iucar@xxxxxxxxxxxxxxxxx> wrote: > > > > I'm not sure what's the issue here: > > > > > > > > - tbb provides libtbb.so.2 > > > > - opencv-core requires libtbb.so.2 > > > > > > > > but [1] pulls opencv-devel and tbb is not pulled too, so the linker > > > > throws the following error: > > > > > > > > libtbb.so.2: cannot open shared object file: No such file or directory > > > > > > > > tbb issue?, opencv issue?, dnf issue?, mock issue?, other? > > > > > > > > [1] https://download.copr.fedorainfracloud.org/results/iucar/cran/fedora-rawhide-x86_64/01694086-R-CRAN-image.textlinedetector/builder-live.log.gz > > > > > > I did local mock fedora-rawhide-x86_64 builds of R-CRAN-curl, > > > R-CRAN-Rcpp, R-CRAN-magrittr, R-CRAN-magick, and finally > > > R-CRAN-image.textlinedetector. The R-CRAN-image.texlinedetector build > > > was successful. I don't know why you are hitting this error in COPR. > > > > Interesting. So mock or Copr? Adding @praiskup to CC. > > That's because your project provides alternative libtbb soname, which is > installed instead of tbb: > > $ dnf repoquery "--disablerepo=*" --enablerepo custom --repofrompath=custom,https://copr-be.cloud.fedoraproject.org/results/iucar/cran/fedora-rawhide-x86_64/ --whatprovides 'libtbb.so.2()(64bit)' 2>/dev/null > R-CRAN-RcppParallel-0:5.0.2-1.fc33.x86_64 You are right, didn't see that. Thanks all for your help. -- Iñaki Úcar _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
