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
In .circleci/config.yml, this will probably require updating the resource class of the apple-darwin executor to use m1. But then the precompiled cross-compiler archive used in that executor will become incompatible (as it's compiled for x86_64). Since the cross-compiler only comes with binaries precompiled for x86_64, we will need to change the way it is installed (archive extraction will have to be replaced with installation from source, which leads to longer execution time, and consequently somewhat more expensive workflows, credit-wise)
The text was updated successfully, but these errors were encountered:
I came across someone else who had difficulties with mac builds on CircleCI: vectordotdev/vector#544
What may not be applicable from the linked issue, though, is the slowness of mac executors (back in the day, there was no M1).
I am very doubtful about my efforts on this task. All of this is just to avoid needing to have Rust installed; or for those with Rust installed, to save a couple of minutes of mac users' time when installing Devnet, and I've already invested entire working days on this, and probably will even more.
Alternative approach
Simply don't build binaries for mac (apple-darwin).
https://discuss.circleci.com/t/macos-intel-support-deprecation-in-january-2024/48718
In
.circleci/config.yml
, this will probably require updating the resource class of the apple-darwin executor to use m1. But then the precompiled cross-compiler archive used in that executor will become incompatible (as it's compiled for x86_64). Since the cross-compiler only comes with binaries precompiled for x86_64, we will need to change the way it is installed (archive extraction will have to be replaced with installation from source, which leads to longer execution time, and consequently somewhat more expensive workflows, credit-wise)The text was updated successfully, but these errors were encountered: