Date: Sun, 05 Apr 2026 07:47:56 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 294255] science/py-scipy fails to build after update to 1.17.1 Message-ID: <bug-294255-21822-tf4gLtCHxQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-294255-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294255 Charlie Li <vishwin@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |vishwin@freebsd.org Flags|maintainer-feedback?(python |maintainer-feedback+ |@FreeBSD.org) | --- Comment #1 from Charlie Li <vishwin@freebsd.org> --- The differences between devel/pybind11 and devel/py-pybind11 primarily lie in where the headers are located. devel/pybind11 has them in the regular system hier(7); devel/py-pybind11 has them in the Python package hierarchy, ie site-packages, also including Python package metadata and a pybind11-config program to assist consumers in finding the headers outside the usual hier(7). The scipy build process in meson-python first queries for the pybind11 Python package, and later during the meson configure process does the header location get established. devel/pybind11 is harmless to this build process as long as the cmake port/package is not present in the environment. Unfortunately meson will prefer to use cmake for dependency detection over pkg-config or other methods like *-config programs, so it is important that, unless a dependency is only meant to be discoverable via cmake, that cmake is not present so meson can use the other methods. It bears repeating that these issues are entirely avoided with environment isolation like poudriere. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294255-21822-tf4gLtCHxQ>