ArchLinux's AUR fails to build broot about broot HOT 4 OPEN

What exact command is used for building broot ?

from broot.

Just cargo build --release, see https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=broot-git#n27
But some build options and environments comes from https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/blob/main/makepkg.conf?ref_type=heads which is where lto comes from, but I don't know enough of its internals to explain how does it interact.
I also wanted to do a manual cargo build while requiring it to do a lto build, but couldn't find the right options or documentations to do so.

from broot.

Here's why I don't understand:

I already build for arch with cargo build --release, you find the result in https://github.com/Canop/broot/releases/tag/v1.36.0
And broot in release mode is always built with the lto option, because of this line: https://github.com/Canop/broot/blob/main/Cargo.toml#L91

from broot.

All I can say is that, on the advice of people on IRC, broot as for the two other rust packages I have with similar issues, is back to building fine if I remove/disable using an exclamation mark lto from this line: https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/blob/main/makepkg.conf?ref_type=heads#L100
This is also the reason distro builds stable releases by adding that option, as visible here: https://gitlab.archlinux.org/archlinux/packaging/packages/broot/-/blob/main/PKGBUILD?ref_type=heads#L15

If you try to build stable's PKGBUILD but remove this line, you should run into the same issue as me.

When I was looking for ways to reproduce this with only cargo, outside of makepkg's environment, I wasn't able to find good ways to do it, but seemed to find things about something like two "levels" of lto, maybemakepkg is trying to do a more "pushed" one which trigger that issue? (I've honestly no idea, here).

from broot.