-
Notifications
You must be signed in to change notification settings - Fork 103
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
cpufetch support for ARM macOS (Apple M1) #47
Comments
Hi, Thanks for posting the issue. cpufetch can't work on the new M1 Macbook. At least for now, the macOS ARM it is not supported. It looks like Apple will continue to release ARM based macOS, so to me is an interestig topic to work on. However, right now I can't work on this since it will proably be a lot of work from my part. I wasn't thinking about adding support for it, but if I can have someone to test stuff and try some patches, I am open to work on this. If you are interested, please leave this issue opened and I will work on it in a few months. I will post a new commit then, so you can try it on your Macbook and check that everything works well. |
I also did try to build it just now and got the same error. I would love to help. |
The issue is not the compilation error. Solving the compilation error is quite easy, but cpufetch will fail since the ARM version is designed to work with Linux only. Now that I know that there are people interested in it, I will try to support it in the future (I hope to commit a new patch in two or three months). However, I would not expect too much functionality to work. Maybe cpufetch will be able to get the number of cores, but not much more than that (because the support is really limited, and it will be literally impossible to get more information. We will see...). Sorry for the inconvenience and thanks for your support! |
hello good day I have the same detail try to compile it on a MacBook Pro M1 |
What you can do is run it in docker
macOS's System Information reports
The difference in cores is obviously down to my Docker setup which I've configured to have 4 cores/2GB memory. The CPU features are also probably not quite right because of the VM setup. |
For the moment, at least it runs, but fetched data are incorrect. For example, the message "Unknown microarchitecture detected" just shows that it tried fetching MIDR registers but instead got all zeros. Frequency is messed up too. I hope that it will run natively in the future... |
NOTE FOR FUTURE VISITORS This is a planned feature to be implemented in |
@Dr-Noob and I have been testing a new version of cpufetch with M1 support, more info to come soon! |
I have good news for those waiting for M1 support. As anticipated by @Kyngo, the M1 port is finished and already integrated into the master branch. Just clone the repo (or update it with PS: I will leave this issue open for a few days until I am sure that everything works correctly, then I'll close it. |
@Dr-Noob I found a problem when building on the
Seems like you forgot to merge something? |
Fixed. The Makefile is more strict in the |
Tested and working like a charm in the master branch. Awesome work! |
@Dr-Noob you should probably update the README file, as it still says M1 is not supported. |
@Dr-Noob there is a small typo in the readme file now, my username is |
Whoops...Fixed! |
Attempting to build on an ARM MacBook Pro shows the below result:
uname -a returns this:
The text was updated successfully, but these errors were encountered: