Opened 4 years ago
Closed 3 years ago
#60834 closed defect (fixed)
py27-tensorflow1: ERROR: tensorflow-1.15.3-cp27-cp27m-macosx_10_13_x86_64.whl is not a supported wheel on this platform.
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | emcrisostomo (Enrico Maria Crisostomo) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | sierra | Cc: | cjones051073 (Chris Jones), mascguy (Christopher Nielsen) |
Port: | py-tensorflow1, py-tensorflow |
Description
ERROR: tensorflow-1.15.3-cp27-cp27m-macosx_10_13_x86_64.whl is not a supported wheel on this platform.
Change History (11)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sierra added |
---|
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
This is still happening, e.g.
- py37-tensorflow1: https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/141879/steps/install-port/logs/stdio/text
- py39-tensorflow1: https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/141876/steps/install-port/logs/stdio/text
Please fix the port or mark it as unbuildable (known_fail yes
) so that the build machine doesn't waste hours of time trying to build this every time the port is modified.
comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | py-tensorflow added |
---|
This is still happening e.g. for py39-tensorflow https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/146689
It's really frustrating to waste 15 hours per subport to rediscover this failed build every time any change is made to these ports.
comment:4 Changed 3 years ago by cjones051073 (Chris Jones)
I know, I do apologise. I am doing my best to try and address this. I thought I had but clearly not. I suspect I might have to resort to manually renaming the file before installing it, as I am sure it actually would install fine if pip would allow it...
comment:5 Changed 3 years ago by cjones051073 (Chris Jones)
comment:6 Changed 3 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:7 Changed 3 years ago by mascguy (Christopher Nielsen)
Can we manually kill the build jobs on the 10.12 builder, until a fix is committed? They're simply going to fail anyway...
comment:8 Changed 3 years ago by cjones051073 (Chris Jones)
sure, I've been keeping an eye out for them..
comment:9 Changed 3 years ago by cjones051073 (Chris Jones)
https://github.com/macports/macports-ports/commit/f160d7e7c85877c271fb34d45f8541752ae40351
I'm hopeful the above will finally address this...
comment:10 Changed 3 years ago by cjones051073 (Chris Jones)
Note, I ideally would set the deployment target bazel uses, but I have failed to get any of the suggestions I can find on how to do this to work...
comment:11 Changed 3 years ago by mascguy (Christopher Nielsen)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The fix addressed the issues, and py-tensorflow
ports are now building successfully on 10.12. Thanks CJones!
Closing as resolved.
Current logs for
py27-tensorflow1 @1.15.4
py36-tensorflow1 @1.15.4
py37-tensorflow1 @1.15.4
py38-tensorflow1 @1.15.4
The problem seems to be that although we are on macOS 10.12 it is compiling with
-mmacosx-version-min=10.13
(which it should not do) which ultimately leads to:We also see in the log:
This is fine since it is using Xcode 9.2 which contains only the 10.13 SDK, but that has nothing to do with the deployment target.