Closed carlosal1015 closed 1 year ago
Mmh, we actually do search for both components. Dune seems to to do the same. I am a bit clueless.
Would you please run CMake with the --trace
option to see where the calls happen.
Ok. It only found the interpreter:
Found Python3: /usr/sbin/python3.10 (found version "3.10.10") found components: Interpreter
I guess the least we can do is to check if Development component was found. We still need to see where the call comes from, as inside OPM we use REQUIRED COMPONENTS
. DUNE skips the REQUIRED
, though.
Would you please run CMake with the
--trace
option to see where the calls happen
Appending --trace
shows the following output.
Thanks.
As it turns out the search is triggered by OPM. The problem is that recent versions with file pybind11NewTools.cmake need the development component even if we just use pybind11_add_module
and don't activate embedded python.
I have created a PR #3478 that should fix this. Would be good if you could test that.
A workaround for the problem would be to activate embedded python with passing the -DPM_ENABLE_EMBEDDED_PYTHON=ON
command line option to cmake. That will also do the search.
Thanks, the issue was solved from my side.
Taking the source
source=(${pkgbase}-release-${pkgver}-rc1.tar.gz::${url}/archive/release/${pkgver}/rc1.tar.gz
pybind11.patch::${url}/pull/3478.patch)
with the patch is sufficient to do the upgrade.
cd ${pkgbase}-release-${pkgver}-rc1
patch -p1 -i ../pybind11.patch
For completeness, providing some logs with the patch.
Thanks a lot :+1: I really like power (linux) users like you. Out of curiosity: Are you (officially) packaging OPM for arch linux?
Since last year I am a normal user as package mantainer in the sense of Arch terminology and not officially in the sense we do not distribute the binaries in the official repositories and claims this caution about the AUR.
Warning: AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.
But, we distribute some dune-modules as signed packages (binaries) in this third-party repository and eventually we will add opm-modules too if you agree.
But, we distribute some dune-modules as signed packages (binaries) in this third-party repository and eventually we will add opm-modules too if you agree.
Cool. The more distributions we are in, the merrier. I don't see a reason why anybody should not appreciate that. Thanks a lot for this work to you and your colleagues.
On the Debian side we usually have some additional patches that might not make it to master. See e.g. file below debian/patches in opm-common and the other repos there.
Hi, I am not sure if the issue belong here or is a pybind's downstream issue, but point to the line 406 and I am leaving this record.
Relevant information
Related links