Package Details: linux-enable-ir-emitter-git 6.0.3.r0.gb8ee83d-1

Git Clone URL: https://aur.archlinux.org/linux-enable-ir-emitter-git.git (read-only, click to copy)
Package Base: linux-enable-ir-emitter-git
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
Provides: linux-enable-ir-emitter
Submitter: nojo
Maintainer: Supdrewin (nojo)
Last Packager: nojo
Votes: 2
Popularity: 0.000000
First Submitted: 2021-06-14 09:17 (UTC)
Last Updated: 2024-09-15 15:59 (UTC)

Latest Comments

1 2 3 Next › Last »

nojo commented on 2024-08-17 12:36 (UTC)

btw this package fails to build even with gcc13 for the latest upstream commit, is someone willing to help with patches?

nojo commented on 2024-08-17 12:35 (UTC)

@MikeWalrus Upstream uses gcc 13 in their CI, so it will involve less patches if this package will use it too. What are significant downsides of using gcc 13 instead of the latest gcc?

MikeWalrus commented on 2024-08-12 22:34 (UTC)

@nojo This one: https://aur.archlinux.org/packages/linux-enable-ir-emitter-git#comment-985922

nojo commented on 2024-08-12 20:21 (UTC)

@MikeWalrus I do not completely understand what patch do you propose. Forcefully enable LTO even if disabled in makepkg.conf?

MikeWalrus commented on 2024-08-11 02:03 (UTC)

@nojo I agree and that’s why I suggest patching the flags in meson.build.

nojo commented on 2024-08-09 15:19 (UTC) (edited on 2024-08-09 15:20 (UTC) by nojo)

You're right - package successfully compiles with lto enabled in /etc/makepkg.conf. Nevertheless, I think it's would be incorrect to both

  • assume that package would always be built with lto

  • forcefully enable lto even if it disabled in makepkg.conf

MikeWalrus commented on 2024-08-09 13:36 (UTC) (edited on 2024-08-09 13:36 (UTC) by MikeWalrus)

not to avoid problems for users with custom config

@FabioLolix Can you elaborate on this? Disabling lto will only break the package and that's probably why nojo has that error. :D

FabioLolix commented on 2024-08-09 13:16 (UTC)

Enabling lto makes the error disappear, so maybe you've disabled it.

lto is enabled by default now, it should be disabled when it cause problems by default not to avoid problems for users with custom config

MikeWalrus commented on 2024-08-09 13:11 (UTC)

I was wrong about gcc 14.2.1 fixing the build. Enabling lto makes the error disappear, so maybe you've disabled it.

I think patching the flags is the best way to go, instead of using an old version of gcc.

You can add a prepare function:

prepare() {
    cd "${srcdir}/${pkgname}"
    sed -i "/language/i \'-Wno-alloc-zero\'," meson.build
}

FabioLolix commented on 2024-08-09 13:02 (UTC)

gcc-14.2.1+r32+geccf707e5ce-1 recognized as C++ compiler for the host machine: c++ (gcc 14.2.1 "c++ (GCC) 14.2.1 20240805") it is the latest in the Arch repo as tested with devtools

1 2 3 Next › Last »