@Neko-san
Unfortunately, I have no idea what's going wrong here.
I've done a quick test by adding the vars/changes from your modified makepkg.conf
to the PKGBUILD directly and then starting a build with makechrootpkg
directly (not using paru
), and that went fine and started building properly. (btw: there's a typo in one of your vars, you have DEBUG_CLAGS
in there at some point, instead of DEBUG_CFLAGS
:)
So either something totally odd is going on, or it's soooomehow caused by the way paru
uses makechrootpkg
(eg. adding -D /mnt/extraStorage/AUR/ParuChroot/repo/aur -d /var/cache/pacman/pkg/
). The changes in the makepkg.conf
, as far as I understand them, shouldn't cause such an issue (lld
, clang
etc are also used by the build anyway, as you've stated already, and all the other ones shouldn't really be relevant for linker functioning).
Pinned Comments
lsf commented on 2025-01-01 21:28 (UTC)
Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.
I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.
Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).