Cannot compile two AUR packages due to compiler options -- where to change?

General system Pacman & AUR helpers
1

On one of my systems, I cannot compile two packages from AUR anymore.

Doesn’t matter if I use paru, yay or makepkg. The compilation stops since the compiler is set to ‘treat warnings as errors’.

I looked in /etc/makepkg.conf, in /etc/pacman.conf and also uninstalled and reinstalled devtools and base-devel. No change. I compared the .conf files with those from a system which worked and couldn’t see a difference.

Where else could that compiler option be set? I would hate to admit defeat and reinstall the system.

2

Can you provide an example of one of the packages?

1 Like
3

Sure. The main culprit is paps which I have installed in version 0.8.0-3, and it’s the update to 0.8.0-4 which fails. But I already asked in the AUR comments, and the maintainer confirmed that it’s working fine on his end as well.

I left two comments there with the version output from the compilers and also the error messages for the run. I hope it’s enough to just post the link.

From what I see, the message cc1plus: Alle Warnungen werden als Fehler behandelt is the important hint.

But grep CXXFLAGS /etc/makepkg.conf results in

CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"

which is the same as on a machine where the compile run goes through. (makepkg.conf.d just contains the standard files rust.conf and fortran.conf).

grep CFLAGS /etc/makepkg.conf:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"

is also the same as on the ‘good’ PC.

Adding -fpermissive to the makepkg.conf CFLAGS doesn’t help, either.

I uninstalled and reinstalled devtools and base-devel with pacman -Rns. Cleaned out the caches from yay and paru and tried makepkg -s. No changes.

4

That package reads a lot of flags from your environment.

Did you check the output of env to see if you have anything interesting in there?

5

paps-git uses and glib2 instead of glibc via fmt as dependency and version 0.8.0 compiles successfully, at least on my system here.

6

Did so now, nothing interesting. Only the usual stuff.

BTW, I still had the welcome greeter active and saw that it clutters my env with 850 (!) variables. Isn’t this a bit excessive?

With greeter: 929 variables :flushed_face:
Without greeter: 79 variables.

Back to topic: Where else could this be set/defined? I also tried grep -nrw ~ -Iie '-Werror' but couldn’t find anything (after clearing out the paru cache).

7

The problem is with this one PC, not with paps in general. paps compiles fine one three other PCs here.

8

I changed paps-git to paps and used cava from extra, so problem averted, but I’d still like to know where the difference to other systems comes from.