Arch Linux User Repository

Please, stop messing with the package and keep it according to packaging guidelines. It works totally fine that way.

Problems with non-default flags (target-cpu=native etc) is not a package area of responsibility. Users overriding the defaults are doing it on their own risk.

According to guidelines export RUSTUP_TOOLCHAIN=stable should also in build() , while here is only in prepare() https://wiki.archlinux.org/title/Rust_package_guidelines#Build

btw a license like MIT which isn't part of the licenses package need to be installed in "${pkgdir}/usr/share/licenses/${pkgname}"

@HuaHuaY if you don't want to switch toolchain you can also build using devtools (using extra-x86_64-build for convenience)

ArchLinuxARM have dropped arm and armv6h

I compile amdgpu_top and meet this error: https://github.com/rust-lang/rust/issues/113152.

I found that pkgbuild has installed a stable toolchain. But it use cargo directly and there is a default nightly toolchain in my computer. So it use nightly channel to compile and then fail due to this error. I think pkgbuild can create a rust-toolchain.toml if you don't want to add this in the github repo. Add echo -e "[toolchain]\nchannel = \"stable-$CARCH-unknown-linux-gnu\"" > rust-toolchain.toml in the build section after cd command. Then the required toolchain and the used toolchain are definitely the same.

On the latest version (0.1.10) this package fails to compile when using RUSTFLAGS="-C opt-level=3 -C target-cpu=znver3" (or target-cpu=native on a Ryzen 5000 CPU). This is an issue in the upstream project/rust compiler and has been reported. UPDATE: The issue is fixed with rustc 1.71

This is a different error though. Seems like there are problems with your crates index.

First of all, try to remove all caches and make a clean build. Also try to build manually using makepkg -siC, without AUR helper.

@Hanabishi I tried this but I still get an error

error: failed to get anyhow as a dependency of package libamdgpu_top v0.1.7 (/home/nora/.cache/paru/clone/amdgpu_top/src/amdgpu_top-0.1.8/crates/libamdgpu_top)

Caused by: failed to query replaced source registry crates-io

Caused by: attempting to make an HTTP request, but --frozen was specified ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'amdgpu_top-0.1.8-1': error: packages failed to build: amdgpu_top-0.1.8-1

The package builds totally fine. Nothing was removed from upstream or crates.io.
This is a local problem of some kind.

Fast search gave me the following:

"It looks like your ~/.cargo/registry/index directory is corrupted. Delete it and run cargo update again."

@blackcatgames seems like the version of a library used by amdgpu_top no longer exists on crates.io or it was renamed. I am currently on holiday without a PC, so I can't fix the package. To fix this you could try amdgpu_top-git but it most likely will have the same issue or modify the PKGBUILD by removing --locked and --frozen from the prepare() and build() functions respectively.

Get the following build error: error: failed to get libdrm_amdgpu_sys as a dependency of package libamdgpu_top v0.1.7 (/home/nora/.cache/paru/clone/amdgpu_top/src/amdgpu_top-0.1.8/crates/libamdgpu_top)

Caused by: failed to query replaced source registry crates-io

Caused by: attempting to make an HTTP request, but --frozen was specified ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'amdgpu_top-0.1.8-1': error: packages failed to build: amdgpu_top-0.1.8-1

if i might say, you made a better program than gpu-z and hwinfo for video card info :)

edit:

i recently took my 6900 xt apart to re-pad it, including its graphite pad with another, and swap the stock fans with 92mm noctua fans. it was SUPER nice to be able to use this to monitor temps before and after the changes in linux. this was the only program on linux that showed me that vrm, memory vrm, soc vrm, and soc temps are actually exposed on linux and can be monitored. prior i had no idea before amdgpu_top. not even lm_sensors showed those temps. originally i was dreading having to boot up windows on another drive just to use something like hwinfo to see those sensors so again, a big thank you for making this.