#61008 closed defect (fixed)
py-numpy build error due to conflict with enum34
| Reported by: | RJVB (René Bertin) | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | py-numpy |
Description
py-numpy fails to build when the enum34 package is installed; see https://github.com/iterative/dvc/issues/1995 for symptoms and description.
This is a tricky one because there is no enum34 port for current python3 versions. Port:py27-numpy can register a build conflict on port:py27-enum34 but the python3 subports would have to do a custom check in the pre-configure or pre-build phase. The error is non-specific enought that this would IMHO be the courteous thing to do, even if users shouldn't install foreign stuff into $prefix (but if you use port:pythonXY as your main Python provide you'll probably end up doing that anyway; I had enum34 installed on 2 independent systems).
Change History (3)
comment:1 Changed 4 years ago by mf2k (Frank Schima)
| Cc: | michaelld removed |
|---|---|
| Owner: | set to michaelld |
| Status: | new → assigned |
comment:2 follow-up: 3 Changed 2 days ago by reneeotten (Renee Otten)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 Changed 2 days ago by RJVB (René Bertin)
Replying to reneeotten:
no idea how old the NumPy version was that you were trying to build
Probably whatever the current version was FOUR (4) years ago?
but nothing depends on
py-enum34anymore, so there shouldn't be an issue.
Nothing depending on py-enum34 anymore (I presume in MP) doesn't mean it can't be installed so I guess users who do will just have to hope that upstream have resolved the issue.
no idea how old the NumPy version was that you were trying to build, but nothing depends on
py-enum34anymore, so there shouldn't be an issue.