Arch Linux User Repository

Hi nardholio! I maintain solana-bin on the AUR (prebuilt CLI tools). Since Anza dropped prebuilt validator binaries in v3.0, I've been looking at how to provide those from source and noticed your package already builds everything. Would you be open to converting solana into a split package (pkgbase=solana)? The natural split follows the existing build phases in your PKGBUILD:

solana — CLI tools (solana, solana-keygen, solana-gossip, solana-faucet, solana-stake-accounts, solana-tokens, spl-token, and optionally agave-install/init). Owns sysusers/tmpfiles. agave-validator — Node operator tools (agave-validator, agave-watchtower, solana-genesis, plus the DCOU/stress-test bins and perf-libs). solana-dev — Program developer tools (cargo-build-sbf, cargo-test-sbf, solana-test-validator, agave-ledger-tool, agave-store-tool, solana-banking-bench, platform-tools-sdk, program deps).

The build() function would stay essentially the same — the three cargo invocations you already have map directly to these groups. Only package() splits into three functions installing different subsets. The main benefit would be that users who just need the CLI don't pull in a validator stack, the DCOU feature boundary is explicit in the packaging, and provides/conflicts can align with solana-bin/solana-dev-bin for users who prefer prebuilt binaries. Happy to help with the implementation or co-maintain. Let me know what you think!

error occurred: Command "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "/home/erik/.cache/yay/solana/src/agave/target/release/build/lz4-sys-c221d104f55beec8/out/include" "-I" "." "-march=x86-64" "-mtune=generic" "-O2" "-pipe" "-fno-plt" "-fexceptions" "-Wp,-D_FORTIFY_SOURCE=3" "-Wformat" "-Werror=format-security" "-fstack-clash-protection" "-fcf-protection" "-fno-omit-frame-pointer" "-mno-omit-leaf-frame-pointer" "-Wp,-D_GLIBCXX_ASSERTIONS" "-std=c++17" "-Wsign-compare" "-Wshadow" "-Wno-unused-parameter" "-Wno-unused-variable" "-Woverloaded-virtual" "-Wnon-virtual-dtor" "-Wno-missing-field-initializers" "-Wno-strict-aliasing" "-Wno-invalid-offsetof" "-msse2" "-std=c++17" "-DLZ4=1" "-DNDEBUG=1" "-DOS_LINUX" "-DROCKSDB_PLATFORM_POSIX" "-DROCKSDB_LIB_IO_POSIX" "-DROCKSDB_SUPPORT_THREAD_LOCAL" "-o" "/home/erik/.cache/yay/solana/src/agave/target/release/build/librocksdb-sys-a78909effa7dfb2a/out/251aeb12ab2525d6-trace_record.o" "-c" "rocksdb/trace_replay/trace_record.cc" with args c++ did not execute successfully (status code exit status: 1).

currently, 2.3.4 version is released, please update it.

The PKGBUILD seems overly complicated. Why not just install with ./scripts/cargo-install-all.sh ?

@alureon Since we want to follow Arch's Rust package guidelines and have some more control. :)

The PKGBUILD seems overly complicated. Why not just install with ./scripts/cargo-install-all.sh ?

That would make this package SO low maintenance.

@ivanmlerner could you add extra archs?

@cjayross To fix the problem with missing BPF SDK, copy or soft link it from the source directory you ran makepkg to /usr/bin/sdk/bpf.

Problem:

BPF SDK path does not exist: /usr/bin/sdk/bpf: No such file or directory (os error 2)

Solution:

git clone https://aur.archlinux.org/solana.git 
cd solana
makepkg -si
mkdir -p /usr/bin/sdk/bpf
cp ./pkg/solana/usr/bin/* /usr/bin/sdk/bpf/

Note: after that, if you run into issues with edition, run rustup default nightly && rustup update

Missing clang makedep.

Unable to build programs with the installation provided.

cargo build-bpf emits

BPF SDK path does not exist: /usr/bin/sdk/bpf: No such file or directory (os error 2)