[MacPorts] #70648: py-contourpy @1.3.0 fails to build: error: 'PYBIND11_MODULE' does not name a type

MacPorts noreply at macports.org
Thu Aug 29 01:21:02 UTC 2024


#70648: py-contourpy @1.3.0 fails to build: error: 'PYBIND11_MODULE' does not name
a type
--------------------------------------------------+------------------------
  Reporter:  barracuda156                         |      Owner:  reneeotten
      Type:  defect                               |     Status:  assigned
  Priority:  Normal                               |  Milestone:
 Component:  ports                                |    Version:  2.10.1
Resolution:                                       |   Keywords:
      Port:  py-contourpy, py-pybind11, pybind11  |
--------------------------------------------------+------------------------
Changes (by reneeotten):

 * cc: stromnov, MarcusCalhoun-Lopez (added)
 * port:  py-contourpy => py-contourpy, py-pybind11, pybind11


Comment:

 Replying to [comment:2 barracuda156]:
 > Looks like `pybind11` was not updated. How was this even supposed to
 work?

 You answered your own question in the upstream ticket: there is both a
 {{{py-pybind11}}} and {{{pybind11}}} port (the lattes one uses Python
 3.11). Most likely you had the {{{pybind11}} port installed and that
 caused the confusion of headers.

 I see two options:
 1. remove the {{{pybind11}}} port and migrate dependents to the {{{pyXY-
 pybind11}}} (sub)port
 2. do the same thing as for {{{py-meson, meson}}} and have the
 {{{pybind11}}} port depend on the subport for MacPorts' default Python
 versions (i.e., currently {{{py312-pybind11}}}) and create the necessary
 symlinks

 I would be in favor of options 1 given the very few dependents and am
 willing to look into doing this, unless there are clear objections and/or
 considerations I am missing.

-- 
Ticket URL: <https://trac.macports.org/ticket/70648#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list