summaryrefslogtreecommitdiff
path: root/core/libseccomp/PKGBUILD
blob: 36c698ba3489183fa2727263c632e823d57fa71f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
#valgrind: fatal error: unsupported CPU.
#   Supported CPUs are:
#   * x86 (practically any; Pentium-I or above), AMD Athlon or above)
#   * AMD Athlon64/Opteron
#   * ARM (armv7)
#   * MIPS (mips32 and above; mips64 and above)
#   * PowerPC (most; ppc405 and above)
#   * System z (64bit only - s390x; z990 and above)
# Test 49-sim-64b_comparisons%%011-00001 result:   FAILURE 49-sim-64b_comparisons rc=1
#
# On i486 we have to ignore valgrind tests, as we don't have i486 support
# for valgrind for now
if [ "${CARCH}" = "i486" ]; then
  eval "$(
    declare -f check | \
      sed '
        s/make check/make check || true/
      '
  )"
fi

# force 2.4.2 version as 2.4.1-4 version to make glibc 2.31 work and
# make it possible to do proper upgrades afterwards to 2.4.2-1
source=(https://github.com/seccomp/${pkgname}/releases/download/v2.4.2/${pkgname}-2.4.2.tar.gz)
pkgrel=4
sha256sums=(b54f27b53884caacc932e75e6b44304ac83586e2abe7a83eca6daecc5440585b)

eval "$(
  declare -f build | \
    sed '
      s/cd ${pkgname}-${pkgver}/cd libseccomp-2.4.2/
    '
)"

eval "$(
  declare -f check | \
    sed '
      s/cd ${pkgname}-${pkgver}/cd libseccomp-2.4.2/
    '
)"

eval "$(
  declare -f package | \
    sed '
      s/cd ${pkgname}-${pkgver}/cd libseccomp-2.4.2/
    '
)"

source+=('libseccomp-2.4.2-ppoll.patch')
sha256sums+=('2d6f638428bc7f9931d4e0a59b80f13327d6c3748e7049eba54b0be08f6620a9')
prepare() {
  cd ${pkgbase}-2.4.2
  patch -Np1 -i "$srcdir/libseccomp-2.4.2-ppoll.patch"
}

# XXX: do NOT trust this key as its not yet in the strong set, see linked issue
# XXX: https://github.com/seccomp/libseccomp/issues/187
# XXX: 47A68FCE37C7D7024FD65E11356CE62C2B524099  Tom Hromatka <tom.hromatka@oracle.com>
# XXX: do NOT trust ^^ this key as its not yet in the strong set ^^ see linked issue
validpgpkeys=('7100AADFAE6E6E940D2E0AD655E45A5AE8CA7C8A') # Paul Moore <paul@paul-moore.com>