Opened 8 years ago
Closed 7 years ago
#52250 closed defect (fixed)
talloc @2.0.8: configure fails if python 3 is selected
| Reported by: | herrbischoff (Marcel Bischoff) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | ||
| Port: | talloc |
Description
On macOS Sierra with Xcode 8.
Attachments (1)
Change History (6)
Changed 8 years ago by herrbischoff (Marcel Bischoff)
comment:1 Changed 8 years ago by herrbischoff (Marcel Bischoff)
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | talloc @2.0.8 build fails → talloc @2.0.8: configure fails if python 3 is selected |
|---|
I'm able to reproduce this failure, if I select a version of python 3 (i.e. sudo port select python python35), so I suggest you don't select a version of python 3. (This causes problem in many places, not just for talloc here.) Either select a version of python 2 or select "none" to allow the macOS version of python 2 to be used.
comment:3 follow-up: 4 Changed 8 years ago by herrbischoff (Marcel Bischoff)
Thanks for the quick response and solution. I have set Python to 'none' and talloc now configures successfully.
Just out of curiosity: shouldn't an environment like MacPorts be able to compensate for this, especially when Python is only needed for the config/build? The different Python forks frustrate me increasingly.
comment:4 Changed 8 years ago by larryv (Lawrence Velázquez)
Replying to marcel@…:
Just out of curiosity: shouldn't an environment like MacPorts be able to compensate for this, especially when Python is only needed for the config/build?
You are correct; the fact that the port is affected by the user’s port select setting is a bug that someone should fix.
comment:5 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This breaks several ports that require it as a dependency, for example
notmuch.