forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/testing/linux-fairphone-fp2/APKBUILD

75 lines
3.6 KiB
Text
Raw Normal View History

fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
# Kernel config based on: arch/arm/configs/lineageos_FP2_defconfig
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
*: remove quotes around pkgname (MR 1186) TP:[AL3]:APKBUILD:5:pkgname must not be quoted [skip ci]: won't finish within 3 hours
2020-04-25 09:51:42 +00:00
pkgname=linux-fairphone-fp2
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
pkgver=3.4.0
linux-*: bump pkgrel for kernels that use downstreamkernel_package (MR 2426) This function was changed, so these packages need to be rebuilt to have the kernel installed under the new filename 'vmlinuz'
2021-09-03 16:55:26 +00:00
pkgrel=13
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
pkgdesc="Fairphone 2 kernel fork"
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
arch="armv7"
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
_carch="arm"
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
_flavor="fairphone-fp2"
url="https://kernel.org"
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
license="GPL-2.0-only"
cross/arch-bin-masquerade, main/anbox-image, linux-*: use pmb:cross-native (MR 1169) https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1910 [skip ci]: CI fails because it can't download every release tarball to check checksums in 3h.
2020-04-21 01:24:27 +00:00
options="!strip !check !tracedeps pmb:cross-native"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev dtbtool xz gcc6"
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
# Compiler: GCC 6 (doesn't boot when compiled with newer versions)
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
if [ "${CC:0:5}" != "gcc6-" ]; then
CC="gcc6-$CC"
Revert "linux-*: use upstream gcc6 [skip ci]" This reverts commit ee659a5bb4ad94f33ec47e6ae7bf9e856f627155 and increases the pkgrels of all affected linux pmaports. I have compiled *every single kernel* that was modified with this commit, and it worked. That took 12 hours. So I'm pretty confident that this is a good commit. Let's roll it out and go back to stability \o/ I'll kick off the binary repo building directly after pushing this, but it will take some time until all binary packages are available again. [skip ci]: it wouldn't finish in time.
2018-11-30 20:56:06 +00:00
HOSTCC="gcc6-gcc"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
fi
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
# Source
_repository="android_kernel_fairphone_msm8974"
_commit="284400aea4b9f8a3c97a34408f48d0971897ae02"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
_config="config-$_flavor.$arch"
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
source="
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
$pkgname-$_commit.tar.gz::https://github.com/LineageOS/$_repository/archive/$_commit.tar.gz
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
$_config
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
gcc7-give-up-on-ilog2-const-optimizations.patch
gcc8-fix-put-user.patch
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-04 12:48:12 +00:00
gcc10-extern_YYLOC_global_declaration.patch
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
kernel-use-the-gnu89-standard-explicitly.patch
linux-fairphone-fp2: fix strace & elogind (MR 1690)
2020-11-08 14:11:47 +00:00
linux3.4-vfs-Fix-proc-tid-fdinfo-fd-file-handling.patch
linux3.4-ptrace-fix-ptrace-defect-cause-by-a-merge-fail.patch
fairphone-fp2: fix swapped red and blue (!292) Fixes the problem described in #211
2019-03-28 15:06:54 +00:00
0001-fix-video-argb-setting.patch
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
0003-Fix-includes.patch
0004-msm-fix-trace.patch
"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
builddir="$srcdir/$_repository-$_commit"
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
prepare() {
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
default_prepare
**/linux-*: update usage of downstreamkernel_prepare helper (!1084) [skip-ci]: just downloading all kernel sources takes about one hour and ollieparanoid wants to merge it now. This already ran successfully with [ci:skip-build] and [ci:skip-vercheck].
2020-04-01 07:09:30 +00:00
. downstreamkernel_prepare
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
# Generate master DTB (deviceinfo_bootimg_qcdt)
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
dtbTool -s 2048 -p "scripts/dtc/" -o "arch/arm/boot/dt.img" "arch/arm/boot/"
}
package() {
device/linux-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
# Master DTB (deviceinfo_bootimg_qcdt)
install -Dm644 "$builddir/arch/arm/boot/dt.img" \
"$pkgdir/boot/dt.img"
Fairphone 2 support (#602) * Started with stock kernel config (fairphone-perf_defconfig) * Enabled DEVTMPFS * Deactivated MSM_KGSL * Enabled the serial console * Enabled USB networking
2017-09-21 17:21:21 +00:00
}
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
sha512sums="6b440c5d087b790894606d4736af815204d9e6f682b7c1ba78f5852fa7aecd74cb276f4953d270f14c96d5418f4e2a83c5179c54d50e2e5afc9084f83ab54200 linux-fairphone-fp2-284400aea4b9f8a3c97a34408f48d0971897ae02.tar.gz
device/*/linux-*: enable CONFIG_DEVPTS_MULTIPLE_INSTANCES for <4.7 (MR 2145) This is required for kernels earlier than 4.7 for bwrap to work for normal users, and therefore for gnome web (epiphany) and flatpak. [ci:skip-build] [ci:ignore-count]
2021-04-29 11:38:24 +00:00
a19a14847492ea383ddffa01f1b8344ca8084ad610b4290e24e5074619295bc5473db186f724211a35a7f0f445a2d0b35e730e7953a3b3ad2f4f70893f07139d config-fairphone-fp2.armv7
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
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-04 12:48:12 +00:00
2b48f1bf0e3f70703d2cdafc47d5e615cc7c56c70bec56b2e3297d3fa4a7a1321d649a8679614553dde8fe52ff1051dae38d5990e3744c9ca986d92187dcdbeb gcc10-extern_YYLOC_global_declaration.patch
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
ad0182a483791fc88e058838bc331b2f04a75ba291e763767babdb815efadfc3b4fda97e69e2e3f00a426cabea088e35297a92bd287592597d1e309be68ee92c kernel-use-the-gnu89-standard-explicitly.patch
linux-fairphone-fp2: fix strace & elogind (MR 1690)
2020-11-08 14:11:47 +00:00
5e81c20b0b30c1ab09bd59f1e1b77fcce945a27de8144c68617ddc5e8f10e1f6fa8b1e4cd5d63e43511d61dace46fb26b14a6227a667b9718d44c8b81dbe6100 linux3.4-vfs-Fix-proc-tid-fdinfo-fd-file-handling.patch
13f82d1ca9b621f026f12f91bbe03d913be41ebed717e9c657e0f3a4d39c0201ba651a7352c2d27b98bb6641b77ccc1b3ee7d4a7c9e91ddb1e347adcb5c9a780 linux3.4-ptrace-fix-ptrace-defect-cause-by-a-merge-fail.patch
fairphone-fp2: fix swapped red and blue (!292) Fixes the problem described in #211
2019-03-28 15:06:54 +00:00
a48336bbfead6ad0c84d2fce0c40a3f5530aebdff356a6835cceaf59a50a6f860d2f8027703a92927955fbb18857ba78788e010d017bf67730f069b36e96fe87 0001-fix-video-argb-setting.patch
Refresh Fairphone 2 packages
2018-08-23 18:40:19 +00:00
403d4999e98ddf73e083076c130a7c9de265096b7abeaabe1ba4305403202e651289a538d104cb37adf783fcecea009f3ed2b722d8640d8d3f12e6cbb8ebe97d 0003-Fix-includes.patch
fairphone-fp2: switch to armv7 (!273) [ci:skip-build]: already built successfully
2019-02-13 18:54:14 +00:00
432099f87fbcd66fa801ecaedb06715754198761c709cbb40b0dc8ffef14a6d6d5f0df27823229b731b18438c705c60c0ce44728b192d8e0f20c285bf761b7f3 0004-msm-fix-trace.patch"
Reference in a new issue Copy permalink