Opened 5 years ago
Closed 5 years ago
#59383 closed defect (duplicate)
py37-rasterio: sh: line 1: 74427 Illegal instruction: 4
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.1 |
Keywords: | Cc: | jmroot (Joshua Root), stromnov (Andrey Stromnov), michaelld (Michael Dickens), reneeotten (Renee Otten) | |
Port: | py-rasterio, py-numpy |
Description
It looks like python3.7 is crashing while trying to configure py37-rasterio on macOS 10.12:
DEBUG: system: cd "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_python_py-rasterio/py37-rasterio/work/rasterio-1.1.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 setup.py --no-user-cfg build sh: line 1: 74427 Illegal instruction: 4 /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 setup.py --no-user-cfg build Command failed: cd "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_python_py-rasterio/py37-rasterio/work/rasterio-1.1.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 setup.py --no-user-cfg build Exit code: 132
Attachments (4)
Change History (14)
comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | python36 python35 added |
---|
comment:2 Changed 5 years ago by reneeotten (Renee Otten)
this looks like the same problem as in ticket:59022 and happens for more Python ports (e.g., py-scipy
) and also there only the py35/py36/py37 version. Therefore I don't think it's a problem with these Python ports per se, it must be something with macOS 10.12 and likely its compiler as it apporeas to happen only for Python ports that build C extensions. I couldn't figure out what the issue is on Ticket 59022.... so any ideas would be welcome; the errors are likely all caused by the same thing.
comment:3 Changed 5 years ago by jmroot (Joshua Root)
Yes, this is near impossible to debug without having a 10.12 installation. A crash log might help though.
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | Python_2019-10-18-231929_sierra.crash added |
---|
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | Python_2019-10-18-222645_sierra.crash added |
---|
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | Python_2019-10-18-222019_sierra.crash added |
---|
Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | Python_2019-10-18-221213_sierra.crash added |
---|
comment:4 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | python38 added |
---|
Attached the 4 most recent Python crash logs from the Sierra buildbot worker.
comment:5 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Maybe a NumPy crash. Maybe https://github.com/numpy/numpy/issues/10330.
comment:6 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | michaelld added |
---|
comment:7 Changed 5 years ago by reneeotten (Renee Otten)
Cc: | reneeotten added |
---|
comment:8 Changed 5 years ago by jmroot (Joshua Root)
Port: | py-numpy added; python38 python37 python36 python35 removed |
---|
It's definitely crashing in numpy code.
comment:9 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Indeed, on my 10.12 test VM I see the same crash:
$ python3.7 Python 3.7.5 (default, Oct 18 2019, 20:43:34) [Clang 9.0.0 (clang-900.0.39.2)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy Illegal instruction: 4
comment:10 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #59022.
Same with python3.5 and python3.6.