-
Notifications
You must be signed in to change notification settings - Fork 709
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
OpenSC build for macOS M1 Pro #3162
Comments
Can you set Xcode as default compiler To OpenSC members: Maybe is time to remove the xcode 12.2 and legacy tokend codepath? |
How would you go about doing that? "Can you set Xcode as default compiler" |
sudo xcode-select -s /Applications/Xcode.app |
So I should run this command: sudo xcode-select -s /Applications/Xcode.app followed by the sudo ./MacOSX/build? |
Select the Xcode then run build script |
Also, any idea if the build for M1 pro and Intel based macs different? The opensc latest dmg doesn't seem to differentiate between whether the .dmg file is applicable to intel processors or M series processors |
It should be universal for both CPU types |
No change even after selecting Xcode as the build Here is the gist https://gist.github.com/ndshah88/3daa771ed3547701dc8c7366c0ac6e65 |
There has been change
probably in your previous build openssl was only built x86_64. |
This log seems to be incomplete. It stops while building OpenSSL without showing an error. You do not require sudo to build OpenSC. |
Hello,
I am trying to build OpenSC on macOS M1 Pro.
When I follow the steps mentioned on this link: https://github.com/OpenSC/OpenSC/wiki/Compiling-and-Installing-on-Unix-flavors
the build is successful but when I try to run the build script within the MacOSx folder: sudo ./MacOSX/build I get the error
https://gist.github.com/ndshah88/cc9d2a98f68470b57ce87a56dc41b763
Here is a log of the same.
Can someone please advise what am I missing?
Also, is the build for M1 pro and Intel based macs different (since the same thing is working perfectly fine on an intel based macOS)
The text was updated successfully, but these errors were encountered: