cli: Remove program arch options - #4295
Merged
acheroncrypto merged 2 commits intoMar 10, 2026
Merged
Conversation
|
@acheroncrypto is attempting to deploy a commit to the Solana Foundation Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
Made an issue to discuss the build-tools version #4298 |
jamie-osec
approved these changes
Mar 9, 2026
akash-osec
pushed a commit
to akash-osec/anchor
that referenced
this pull request
Mar 25, 2026
akash-osec
pushed a commit
to akash-osec/anchor
that referenced
this pull request
Jul 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
cargo-build-bpfno longer exists, which makes the--archoption in various commands useless. It might also be confused with the--archoption of the underlyingcargo-build-sbfcommand:Summary of changes
Remove the program
--archoptions from all the commands that have it.Related: Hardcoding build tools version (#4098) is far from ideal because:
-- --tools-versionto the underlying command, which we support.However, this problem is out-of-scope of this PR; I might make another PR to handle this better.