Package Details: arm-linux-gnueabihf-linux-api-headers 4.12.7-1

Git Clone URL: https://aur.archlinux.org/arm-linux-gnueabihf-linux-api-headers.git (read-only)
Package Base: arm-linux-gnueabihf-linux-api-headers
Description: Kernel headers sanitized for use in userspace (arm-linux-gnueabihf)
Upstream URL: http://www.gnu.org/software/libc
Licenses: GPL2
Submitter: tavianator
Maintainer: tavianator
Last Packager: tavianator
Votes: 26
Popularity: 0.881415
First Submitted: 2015-09-14 15:33
Last Updated: 2017-09-23 13:55

Latest Comments

zours commented on 2016-06-23 15:09

@Duality:
gpg --recv-keys 79BE3E4300411886
gpg --recv-keys 38DBBDC86092693E

tavianator commented on 2016-05-18 23:35

@Duality: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

Duality commented on 2016-05-18 22:08

anyone else experiencing this:

==> Making package: arm-linux-gnueabihf-linux-api-headers 4.5.2-1 (Thu May 19 00:07:30 CEST 2016)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found linux-4.5.tar.xz
-> Found linux-4.5.tar.sign
-> Found patch-4.5.2.xz
-> Found patch-4.5.2.sign
==> Validating source files with md5sums...
linux-4.5.tar.xz ... Passed
linux-4.5.tar.sign ... Skipped
patch-4.5.2.xz ... Passed
patch-4.5.2.sign ... Skipped
==> Verifying source file signatures with gpg...
linux-4.5.tar ... FAILED (unknown public key 79BE3E4300411886)
patch-4.5.2 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!

tavianator commented on 2016-03-23 18:43

@srgk: linux-api-headers is not updated every time the kernel is, so this package is not out of date.

pmattern commented on 2015-09-20 17:25

Alright. Thanks for clarifying.

tavianator commented on 2015-09-18 22:46

@pmattern: That comment comes from the PKGBUILD for the core linux-api-headers (https://projects.archlinux.org/svntogit/packages.git/tree/linux-api-headers/trunk/PKGBUILD#n4), which this is partially based on. I agree it's confusing in the context of this cross toolchain, and I'll remove it for the next release!

pmattern commented on 2015-09-18 17:41

The build order as stated in PKGBUILD, apparently a remnant of the old AUR 3, seems a bit odd to me. It's different from https://wiki.archlinux.org/index.php/Cross-compiling_tools_package_guidelines#Building_a_cross_compiler and e. g. the need to compile binutils twice is something I for one have never before.
IMO that line is pretty useless anyway and should simply get dropped the next release or so. The distinct order is depending on the toolchain the package shall be part of, first time users will stumble upon the order while reading documentation which is obligatory, experienced users will know the order by heart.