Closed pikumar closed 2 years ago
Hi Piyush!
It sounds like a segyio
issue, it is trying to build it from the source. Kinda surprised it is not getting a wheel.
What CPU architecture are you on? Maybe segyio
doesn't have wheels for that.
I had a similar issue with OS X ARM64 (M1) architecture and opened this issue https://github.com/equinor/segyio/issues/534
EDIT: Looking at it you are on OS X ARM64. Yes that is expected. Unfortunately won't be able to fix until the segyio
team provides an OS X ARM64 build. In the meantime you can install the build dependencies for segyio
manually.
Another solution is to run the x86_64 version of Python with Rosetta 2 emulator. That works fine, but it will probably run a little slower.
Thanks Altay. Indeed I am on an M2 Air. Hoping that segyio fixes this soon. Will keep my fingers crossed.
No problem, closing the issue for now since it is resolved!
Thanks @pikumar
I had the same problem on M1 Max and created an environment using conda and set the architecture to x86_64 using the following lines of code.
CONDA_SUBDIR=osx-64 conda create -n myenv_x86 python=3.9
conda activate myenv_x86
conda config --env --set subdir osx-64
@AmirMardan, thanks for the workaround. I guess that this runs the x86_64 version using Rosetta 2. While it may work, it probably won't perform as fast as the native :)
The last time I checked on my Mac, segyio
was compiling on ARM64 ok; hence mdio
should work ok as well. Are you seeing a similar issue with the latest segyio
?
Yes, I had the same problem and I had to create another environment with osx-64
to make it work.
segyio 1.9.12+ now works with ARM64 on Mac OS.
Just confirming that on an M2 mac air, with Python 3.11.6 - pip install worked flawlessly. Thanks.
I think I can install skbuild manually and fix this, but was wondering if this was going to be an issue for others?