You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On machines running macOS with Apple Silicon processors, it might happen that the Python executable is run in x86_64 compatibility model, e.g. because the x86_64 version of Conda, and consequently Python, gets installed
This causes an issue for idaes get-extensions: in this scenario, the current architecture detection logic only "sees" x86_64 and downloads the corresponding binaries, which causes many things not to work properly (see Unable to load HSL solvers for IPOPT on M1 Mac #1494)
Possible solution/remedies
Enable idaes get-extensions to detect when it's being run in this scenario (i.e. x86_64 executable on an Apple Silicon machine) and error out and/or warn the user
Implementation considerations
There might be heuristics we can use to work around the inability to detect the machine architecture directly in this scenario: for example, macOS versions starting from 10.14 only run on Apple Silicon
Therefore, if the detected OS version is 10.14 and the detected machine architecture is x86_64, it is likely (or possibly certain?) that the code is running in this "unwanted compatibility mode" scenario and idaes get-extensions can warn/error out accordingly
Motivation
idaes get-extensions
: in this scenario, the current architecture detection logic only "sees" x86_64 and downloads the corresponding binaries, which causes many things not to work properly (see Unable to load HSL solvers for IPOPT on M1 Mac #1494)Possible solution/remedies
idaes get-extensions
to detect when it's being run in this scenario (i.e. x86_64 executable on an Apple Silicon machine) and error out and/or warn the userImplementation considerations
idaes get-extensions
can warn/error out accordinglyProposed next steps
The text was updated successfully, but these errors were encountered: