-- Found JPEG: /usr/lib64/libjpeg.so (found version "62") -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success CMake Error at src/occt_wrapper/CMakeLists.txt:22 (find_package): By not providing "FindOpenCASCADE.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "OpenCASCADE", but CMake did not find one. Could not find a package configuration file provided by "OpenCASCADE" (requested version 7.6.2) with any of the following names: OpenCASCADEConfig.cmake opencascade-config.cmake Add the installation prefix of "OpenCASCADE" to CMAKE_PREFIX_PATH or set "OpenCASCADE_DIR" to a directory containing one of the above files. If "OpenCASCADE" provides a separate development package or SDK, be sure it has been installed. Reproducible: Always
Created attachment 801820 [details] build.log.gz
Created attachment 801823 [details] emerge-info.txt
Confirming that I'm also getting this error. Tried installing sci-libs/opencascade-7.6.3:0/7.6::gentoo but got this error when retrying the install: CMake Error at src/occt_wrapper/CMakeLists.txt:22 (find_package): Could not find a configuration file for package "OpenCASCADE" that is compatible with requested version "7.6.2". The following configuration files were considered but not accepted: /usr/lib64/cmake/opencascade/OpenCASCADEConfig.cmake, version: 7.6.3 installing sci-libs/opencascade-7.6.2-r1:0/7.6::gentoo allowed me to upgrade prusa-slicer to the new version.
*** Bug 867310 has been marked as a duplicate of this bug. ***
fwiw it builds fine with 7.6.3 if bypass the check (haven't tried runtime), unsure if upstream has a reason for pinning to exactly 7.6.2 rather than >=7.6.2 <7.7 or so at most if still want it strict
Also, qa-vdb reports (app-portage/iwdevtools): * VDB: detected possibly incorrect RDEPEND (media-gfx/prusaslicer-2.5.0_rc1) * dev-libs/imath:3= < * > media-libs/libjpeg-turbo:= * > sci-libs/opencascade:= * sys-libs/zlib < * virtual/glu < So also missing libjpeg-turbo, the rest may or may not be removable.
https://git.dev.opencascade.org/gitweb/?p=occt.git;a=blob;f=CMakeLists.txt;h=23dd2d377b8e254ca18c818c84803d52e579fd1a#l1289 states that it only matches the exact version. Therefore it must be fixed to 7.6.2 for now.
(In reply to Dennis Lamm from comment #7) > https://git.dev.opencascade.org/gitweb/?p=occt.git;a=blob;f=CMakeLists.txt; > h=23dd2d377b8e254ca18c818c84803d52e579fd1a#l1289 states that it only matches > the exact version. Therefore it must be fixed to 7.6.2 for now. The question is whether that's a good upstream decision based on something immovable or whether they're just doing it out of "safety" (pre-emptive version pinning for no good or specific reason).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=205c11fa0a4555a97fad6552783075864d4f0d38 commit 205c11fa0a4555a97fad6552783075864d4f0d38 Author: Dennis Lamm <expeditioneer@gentoo.org> AuthorDate: 2022-08-31 18:01:52 +0000 Commit: Dennis Lamm <expeditioneer@gentoo.org> CommitDate: 2022-08-31 18:26:47 +0000 media-gfx/prusaslicer: fixed dependencies Bug: https://bugs.gentoo.org/867301 Signed-off-by: Dennis Lamm <expeditioneer@gentoo.org> Package-Manager: Portage-3.0.30, Repoman-3.0.3 Closes: https://github.com/gentoo/gentoo/pull/27090 Signed-off-by: Dennis Lamm <expeditioneer@gentoo.org> media-gfx/prusaslicer/prusaslicer-2.5.0_rc1.ebuild | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
(In reply to Sam James from comment #8) > (In reply to Dennis Lamm from comment #7) > > https://git.dev.opencascade.org/gitweb/?p=occt.git;a=blob;f=CMakeLists.txt; > > h=23dd2d377b8e254ca18c818c84803d52e579fd1a#l1289 states that it only matches > > the exact version. Therefore it must be fixed to 7.6.2 for now. > > The question is whether that's a good upstream decision based on something > immovable or whether they're just doing it out of "safety" (pre-emptive > version pinning for no good or specific reason). I wouldn't be too fixed on what upstream says, remember that upstream in even this release do not support new boost, chance why it is so heavy patched in this areas.
It looks like the media-gfx/prusaslicer-2.5.0-r1 builds and runs fine against sci-libs/opencascade-7.7.0 as well... Could you consider to relax the DEPENDs to include it too? i.e to `>=sci-libs/opencascade-7.6.2:=
I seen your comment by accident. Create a new bug for it and I will take care of it.
Closing the bug as it in fact now depends on it. relaxing of this dependency is separated from this one.
(In reply to Piotr Karbowski from comment #12) > I seen your comment by accident. Create a new bug for it and I will take > care of it. done; See bug #892647 PS: A knew I should probably fill it as a separate bug from the beginning... but against me better judgement I've decided that it would be too big of a hassle for such a small issue..
