Search Criteria
Package Details: solana-dev-bin 4.2.2-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/solana-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | solana-bin |
| Description: | Solana developer tools: SBF compiler toolchain, test validator, and ledger tool |
| Upstream URL: | https://solana.com |
| Keywords: | blockchain mainnet rpc solana validator |
| Licenses: | Apache-2.0 |
| Conflicts: | solana |
| Submitter: | vbmithr |
| Maintainer: | aarto |
| Last Packager: | aarto |
| Votes: | 2 |
| Popularity: | 1.00 |
| First Submitted: | 2021-02-27 12:52 (UTC) |
| Last Updated: | 2026-10-13 15:53 (UTC) |
Dependencies (6)
- glibc (glibc-gitAUR, glibc-git-native-pgoAUR, glibc-eacAUR)
- libgcc (libgcc-fast-optimizedAUR, libgcc-snapshotAUR)
- libstdc++ (libstdc++-fast-optimizedAUR, libstdc++-snapshotAUR)
- openssl (openssl-gitAUR, openssl-aegisAUR, openssl-staticAUR)
- rustup (rustup-gitAUR) (optional) – required for cargo-build-sbf and cargo-test-sbf
- solana-binAUR (optional) – CLI tools for interacting with clusters
Latest Comments
1 2 3 Next › Last »
aarto commented on 2026-10-13 15:59 (UTC)
Hi @recallmenot, fixed in 4.2.2-2, thanks for the report.
solana-dev-binis a separate package but shares a PKGBUILD withsolana-bin, so a failure in one breaks both. I only saw your comment now because notifications were off for this package, they're on now.recallmenot commented on 2026-10-05 22:09 (UTC)
thought solana-dev-bin was supposed to be a different package?
yay -S solana-bin ... ==> Starting package_solana-dev-bin()... cp: cannot stat 'bin/platform-tools-sdk/sbf': No such file or directory ==> ERROR: A failure occurred in package_solana-dev-bin(). Aborting... -> error making: solana-bin-exit status 4 -> Failed to install the following packages. Manual intervention is required: solana-bin - exit status 4
esemeniuc commented on 2023-02-27 01:14 (UTC)
Yes. The git history could also be ported I believe. Not sure if it would require orphaning this package.
vbmithr commented on 2023-02-25 11:07 (UTC)
Possible, yes. That means creating a new package with a different name, right?
esemeniuc commented on 2023-02-24 23:07 (UTC)
@vbmithr v1.14.16 is tagged for mainnet, do you want to rename this package to
solana-mainnet-binto avoid confusion with other branches?esemeniuc commented on 2023-01-10 04:29 (UTC)
@ivanmlerner noted, I'll make a new package on the 1.15 cycle when it is ready for testnet, and let this stay on the 1.14 branch
ivanmlerner commented on 2022-12-21 15:36 (UTC)
@esemeniuc I think it would be better to track mainnet on this one and create another package tracking testnet. I'll do this for the source package.
vbmithr commented on 2022-10-17 16:14 (UTC)
Here you go!
esemeniuc commented on 2022-10-15 20:43 (UTC)
Can you add me as a co-maintainer? Package is out of date and having conflicts with anchor
1 2 3 Next › Last »