-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: open apexypy on macOS silicon #129
Comments
PS: The problem occurs at the import. It installs normally with |
I recommend following the instructions here to ensure you're using compatible compilers. This is usually the issue with macs: https://apexpy.readthedocs.io/en/latest/installation.html#specifying-compilers |
Unfortunately, this doesn't work. Even if I build the package using meson and ninja (successfully), an |
Can you show me which compilers your system is using? This should be the top level output from meson. |
meson setup build
ninja -j 2 -C build executes, but I get the following warnings:
meson install:
|
Here's the problem:
You need to specify the C compiler to match the fortran compiler, both need to be GCC. |
Ok, I did, but without success. meson setup build
meson install:
However, python doesn't find apexpy now. It looks meson installs it in |
Ok, so I don't know how to change where pip or meson installs site packages. You can add that path to your python path and that is one way forward. However, I think I have the right tricks now to let you use pip directly via:
On a recent M1 Mac with Anaconda Python, I ran into the following additional issues:
This allowed the conda pip to install apexpy using the specified compilers and run successfully. If number (2) is an issue, you'll see apexpy look like it installs successfully. Then, when you import you'll get an error message that it can't read the fortran file because of the architecture. |
apexpy returns an error at import:
import apexpy
ERROR:
NOTE:
fortranapex compiles normally from /frotranapex/ using make.
Using :
Python 3.11.5 (main, Sep 11 2023, 08:31:25) [Clang 14.0.6 ] on darwin
This must be a problem similar to #16
Likely the problem with linking to the correct compiler/path in setup.cfg
The text was updated successfully, but these errors were encountered: