Search Criteria
Package Details: system76-power 1.1.26-1
| Git Clone URL: | https://aur.archlinux.org/system76-power.git (read-only, click to copy) |
|---|---|
| Package Base: | system76-power |
| Description: | System76 Power Management |
| Upstream URL: | https://github.com/pop-os/system76-power |
| Licenses: | GPL |
| Submitter: | ebobby |
| Maintainer: | tleydxdy |
| Last Packager: | tleydxdy |
| Votes: | 12 |
| Popularity: | 0.001641 |
| First Submitted: | 2018-07-05 23:47 (UTC) |
| Last Updated: | 2024-03-11 19:25 (UTC) |
Dependencies (7)
- dbus (dbus-gitAUR, dbus-x11-gitAUR, dbus-selinuxAUR)
- libusb (libusb-gitAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- rust (rust-nightlyAUR, rust-nightly-binAUR, rust-gitAUR, rustup-gitAUR, rustup) (make)
- system76-acpi-dkmsAUR (system76-acpi-dkms-gitAUR) (optional) – some systems might need this driver
- system76-dkmsAUR (system76-dkms-gitAUR) (optional) – some systems might need this driver
- system76-io-dkmsAUR (system76-io-dkms-gitAUR) (optional) – some systems might need this driver
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
lethedata commented on 2022-01-15 14:18 (UTC)
@tleydxdy I don't have enough of an understanding of rust to know exactly why, but it seems to be related rusts linker-plugin-lto or LLVM not working correctly with the devtools implementation. devtools probably has a flag enabled that either just breaks things or requires rust to have additional arguments to work properly. Alternatively, makechrootpkg might spawn in such a way that rust's linker is unable to find what is needed to successfully link.
The aurutils issue reference from earlier makes use of makechrootpkg, which is what the Convenience Way of Building in a clean chroot does. I did test both ways and only the classic way worked.
Sources: (Solved) Can't link any Rust program linker-plugin-lto stopped working in Rust 1.45.0 -Clinker-plugin-lto doesn't work without extra manual work Regression on nightly since LLVM 8 upgrade: thread sanitizer doesn't compile anymore
tleydxdy commented on 2022-01-07 02:42 (UTC)
@echo can you explain a little more about the issue? lto seems like a nice to have, why is it not working in this particular case?
lethedata commented on 2022-01-07 01:55 (UTC)
Rust fails to link (
error: linking with 'cc' failed: exit status: 1) when using devtools due to lto being enabled by default. Addingoptions=(!lto)to PKGBUILD allows it compile.Issue Reference
yochananmarqos commented on 2021-09-19 19:13 (UTC)
@tleydxdy: Ah, I didn't see that commit earlier.
I just built it without that just fine, odd.
tleydxdy commented on 2021-09-19 18:19 (UTC)
@yochananmarqos it is how it was done upstream, this is just a temporary hack before they make the next release. 1.1.18 has a mistake in it and won't actually build
yochananmarqos commented on 2021-09-19 18:16 (UTC)
@tleydxdy: Why are you specifying a static toolchain version? Just use:
See Rust package guidelines
tleydxdy commented on 2021-06-20 08:13 (UTC)
@hossamdash pushed a fix
hossamdash commented on 2021-06-19 23:13 (UTC)
@tleydxdy yes i just checked out the commit that was 7 weeks ago and installed it. it works fine and the service starts without any problems.
« First ‹ Previous 1 2 3 4 5 6 Next › Last »