-
Notifications
You must be signed in to change notification settings - Fork 270
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
Including cpuinfo_arm.h from an Apple M1 target. #179
Comments
seem related to #121 cpu_features/include/cpuinfo_arm.h Lines 117 to 119 in 628c50e
cpu_features/include/cpu_features_macros.h Lines 38 to 40 in 1199437
|
... and how would one set an environment variable that un-sets these flags? |
Sorry I mean it is a two folds problem: First CMake detect (at configure time) your current host platform as Lines 57 to 58 in 628c50e
then we add the corresponding file to the source list Lines 73 to 75 in 628c50e
then in each cpuinfo_*.h file we check (at compile time i.e. cmake build time) if we support the currently compiler detected arm flavor...
Questions:
note: Our current CMake implementation suppose it is also the target platform otherwise you'll need a CMake Toolchain file with EDIT: To answer your question you don't "set an environment variable that un-sets these flags", actually there are given by your compiler x platform x OS and you do your best as the developer to deal with it. So to summary since we still don't have an M1 to test/adapt the source code and the CMake build, the current support is on a best effort basis with the help of the community. |
Is this issue addressed by PR #150? |
While installing some other node dependencies, one of them attempts to build
cpu_features
usingnode-gyp
and fails with the following message. Is there an environment variable the code will look for to control this, or is it simply an issue onApple M1
or am I jus totally off-base?The text was updated successfully, but these errors were encountered: