Opened 19 months ago
Closed 19 months ago
#67364 closed defect (fixed)
cdo @2.2.0: configure: error: no suitable Python interpreter found
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | tenomoto (Takeshi Enomoto) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | remkos (Remko Scharroo) | |
Port: | cdo |
Description
cdo @2.2.0 fails to build on Mojave and earlier:
checking for a Python interpreter with version >= 3.6... none configure: error: no suitable Python interpreter found
Apple did not start including python 3 in macOS until Catalina.
On older systems (or unconditionally if you prefer) you can use the MacPorts python311 port.
You will need to inform the build of the absolute path of whichever python you want it to use.
Change History (2)
comment:1 Changed 19 months ago by remkos (Remko Scharroo)
comment:2 Changed 19 months ago by Remko Scharroo <remko.scharroo@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Ah ... that must be something new. Thanks for the reporting.
I checked the code and found that python is only used for testing. So it was easy enough the add it as a depend_build. As pointed out, I also now added the full path as an environment variable. It tested out fully on my side. Granted, this is on Ventura.
En passant, I also changed the test.dir to the default, since it changed in the upstream release.
See PR https://github.com/macports/macports-ports/pull/18511