-
Notifications
You must be signed in to change notification settings - Fork 65
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
Build Error (cpuid.h: No such file or directory) #153
Comments
What is the architecture of your system? Not sure if this is related, but can you try the suggestions from this issue #142. |
My architecture is ARM64, I use the VM on the M1 Macbook |
Thanks for the info. I don't have access to an M1 Mac and thus haven't tried to build AMBF on a VM. Did you try the solution to Issue #142 and did it change anything? If that doesn't work for you, I know of a couple of people who tried running AMBF via Docker on the M1 Mac. You can find the instructions for that here: |
I will have a try and let you know the further result, thanks for your help! |
Great, could you also try this on your VM. In your local AMBF copy, can you comment out this line: https://github.com/WPI-AIM/ambf/blob/ambf-2.0/external/openal/include/alConfig.h#L74 in the file
to
and see if this allows you to compile. |
@adnanmunawar I had the same issue and tested this workaround on my M1 mac mini running parallels VM Ubuntu 20.04 and it works. |
Thanks, Radian, the new commit should incorporate these changes. |
@adnanmunawar hi Adnan, this commit did not prevent the error for me. However, commenting out those lines again did work. I guess the commit implementing the if statement does not always work. Just wanted to let you know. I'm using a M1 macbook air running Ubuntu 18.04 on VMWare Fusion. |
Thanks for reporting this Youp, I shall take a look at it. I might need your help to test it though as I do not have an M1 Mac :) |
Hi, when I install ambf-2.0 on Ubuntu 20.04, it gave an error that the "cpuid.h" is missing. Could you please help me solve it?
The text was updated successfully, but these errors were encountered: