envolution: checksum was correct until the additional commits bumping the version, but it is fixed now pointing to the new release.
![]() |
VOOZH | about |
| Git Clone URL: | https://aur.archlinux.org/linux-enable-ir-emitter.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-enable-ir-emitter |
| Description: | Enables infrared cameras that are not directly enabled out-of-the box |
| Upstream URL: | https://github.com/EmixamPP/linux-enable-ir-emitter |
| Keywords: | cameras infrared |
| Licenses: | MIT |
| Conflicts: | chicony-ir-toggle, linux-enable-ir-emitter-git |
| Submitter: | renyuneyun |
| Maintainer: | iyanmv |
| Last Packager: | iyanmv |
| Votes: | 12 |
| Popularity: | 0.035390 |
| First Submitted: | 2021-06-12 17:19 (UTC) |
| Last Updated: | 2025-09-03 12:05 (UTC) |
envolution: checksum was correct until the additional commits bumping the version, but it is fixed now pointing to the new release.
b2sum issue in PKGBUILD for the patch file, should be
9690a13ec65b7135aadd63486a29c4f4b3688e5cfb4668e9869eb19dda9b8eeac73a42e3057cf7c907907072eeac569908679b487b224ddd4053dd8f705618d9
After updating the system, sudo systemctl status linux-enable-ir-emitter.service prompts
linux-enable-ir-emitter[1396]: linux-enable-ir-emitter: error while loading shared libraries: libfmt.so.10: cannot open shared object file: No such file or directory
Solved by rebuilding
a15355447898a: I also cannot replicate your issue with yay. Have you tried doing a clean build with yay? Have you modified makepkg.conf or any other relevant config files? In any case, I don't think this is an issue with the current PKGBUILD so I will not add your suggestion.
@iyanmv: I get this error using yay, I don't get it using extra-x86_64-build
a15355447898a: are you using an AUR helper? If so, which one? Do you observe the same error if you build it in a clean chroot env, for example, with extra-x86_64-build?
@iyanmv : I don't know, I got this error after updating the arch this afternoon.(stable version)
Hi a15355447898a: can you elaborate a little bit? When are these errors expected to happen (next release, future gcc version)? I just tried to rebuild the package on a clean env and I don't experience those issues with current stable repos enabled.
There will be the following errors during construction
usr/include/c++/14.1.1/bits/regex_executor.tcc:155:17:
/usr/include/c++/14.1.1/bits/regex_executor.h:244:31: 错误:argument 1 value is zero [-Werror=alloc-zero]
244 | : _M_visited_states(new bool[__n]()), _M_start(__start)
| ^~~~~~~~~~~~~~~
In file included from /usr/include/c++/14.1.1/bits/new_allocator.h:34,
from /usr/include/c++/14.1.1/x86_64-pc-linux-gnu/bits/c++allocator.h:33,
from /usr/include/c++/14.1.1/bits/allocator.h:46,
from /usr/include/c++/14.1.1/memory:65,
from ../linux-enable-ir-emitter-6.0.0/camera/camera.hpp:4,
from ../linux-enable-ir-emitter-6.0.0/camera/camera.cpp:1:
Please modify PKGBUILD
build() {
mkdir -p build
#arch-meson $pkgname-$pkgver build
arch-meson $pkgname-$pkgver build -Dcpp_args="-Wno-error=alloc-zero"
meson compile -C build
}
My computer cannot work with the latest version but version 4.1.5. Others who encounter difficulties may consider downgrading and modifying PKGBUILD.