pmaports/device/testing/linux-meizu-turbo
Luca Weiss 81f8ca8e77
device/testing/linux-*: get building again (MR 1684)
Mostly the GCC10 yylloc failure was seen but several others have been
observed:

* wireguard script was silently failing
* several gcc10 x86 errors
* a checksum from kernel.org has changed

Now we have 3 different gcc10 yylloc patches:

gcc10-extern_YYLOC_global_declaration.patch:
    Linux < 4.2

linux4.2-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.2+

linux4.17-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.17+

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]
2020-11-05 09:55:11 +01:00
..
0001-Get-rid-of-Android-toolchain-binaries-in-Makefile.patch
0002-Make-exynos_ufs_ctrl_hci_core_clk-visible-to-other-T.patch
0003-Remove-hard-coded-denial-of-ro-attr-change-for-SD.patch
0004-Remove-loopy-symlink.patch
0005-Use-Samsung-MFC-from-A810.patch
APKBUILD
config-meizu-turbo.aarch64
gcc7-give-up-on-ilog2-const-optimizations.patch
gcc10-extern_YYLOC_global_declaration.patch