Arch Linux User Repository

Please read the AUR wiki page before reporting issues.

If you are experiencing a build issue then ensure you are not using an AUR helper and are using a clean chroot.

Build fails here too with

==> Verifying source file signatures with gpg...
    gcc-9.3.0.tar.xz ... FAILED (unknown public key A328C3A2C3C45C06)
==> ERROR: One or more PGP signatures could not be verified!

I don't use an AUR helper, only plain makepkg.

I was trying to build gcc9. However, it failed with

==> Verifying source file signatures with gpg...
    gcc-9.3.0.tar.xz ... cat: write error: Broken pipe
FAILED
==> ERROR: One or more PGP signatures could not be verified!

OK, I've been trying for a week or so to get the patch that's now included in gcc=11 to make a difference to this package, but the only way that worked for me was to force it via flags in the PKGBUILD.

There's no need to rebuild (no no pkgrel bump), but new builds should work again.

I'm keeping an eye on FS#70701 to see what the approach will be. Switching CFLAGS seems like a workaround.

Hi,

The build fails with error: format not a string literal and no format arguments [-Werror=format-security]:

/home/dan/temp/gcc9/src/gcc/libcpp/expr.c: In function ‘unsigned int cpp_classify_number(cpp_reader*, const cpp_token*, const char**, location_t)’:
/home/dan/temp/gcc9/src/gcc/libcpp/expr.c:797:18: error: format not a string literal and no format arguments [-Werror=format-security]
  797 |        0, message);
      |                  ^
/home/dan/temp/gcc9/src/gcc/libcpp/expr.c:800:39: error: format not a string literal and no format arguments [-Werror=format-security]
  800 |           virtual_location, 0, message);
      |                                       ^
cc1plus: some warnings being treated as errors

Building "clean", with

git clone https://aur.archlinux.org/gcc9.git; cd gcc9/; makepkg

Cannot replicate a build failure caused by the expired key:

==> Verifying source file signatures with gpg...
    gcc-9.3.0.tar.xz ... Passed (WARNING: the key has expired.)

An expired key for a release signature would seem to be an upstream issue rather than a packaging issue.

@jonathon the key is correct but the .sig was signed with a timestamp which is no longer valid. That avoid to build in a clean chroot without change the PKGBUILD removing the signature or adding the key manually in a non-chroot.

@brianmsm Thanks! Adding the key manually allows it to work.

Please read the AUR wiki page before reporting issues.

If you are experiencing a build issue then ensure you are not using an AUR helper and are using a clean chroot.

The key is correct. Please see https://gcc.gnu.org/mirrors.html for a full list of valid signing keys.