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

53 lines
1.8 KiB
Text
Raw Normal View History

New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
# Kernel config based on: arch/arm/configs/notle_defconfig
*: 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-google-glass
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
pkgver=3.4.83
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405) Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using aes-xts-plain64 as default cipher for cryptsetup (override with "pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940). I have executed "pmbootstrap kconfig edit" on each kernel, and manually toggled the option. The diff is not always clean, because for some kernels it is apparently the first time, that menuconfig was executed on the configs like that. In a few instances, it turned out that CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is already a requirement, but as the config was incomplete, it was not visible that this option was enabled). Very few times, I had to enable CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS. It would be great if we could automate such mass kconfig edits in the future, see pmbootstrap#1942. [skip ci]: I have verified, that every single one of these kernels builds. CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
pkgrel=4
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
pkgdesc="Google Glass kernel fork"
arch="armhf"
_carch="arm"
_flavor="google-glass"
url="https://kernel.org"
license="GPL2"
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-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev gcc6"
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
# Compiler: this kernel was only tested with GCC6. Feel free to make a merge
# request if you find out that it is booting working with newer GCCs as
# well. See <https://postmarketos.org/vendorkernel> for instructions.
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
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
# Source
_repository="factory-kernel"
_commit="1091b53a0b5e20d23a8447161e181e2a53e944de"
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"
New device: Google Glass (#957)
2017-12-01 19:15:42 +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/GlassHack/$_repository/archive/$_commit.tar.gz
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
$_config
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
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
"
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"
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
prepare() {
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
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
}
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"
New device: Google Glass (#957)
2017-12-01 19:15:42 +00:00
}
sha512sums="b98916d6cc745115e89be35158b4cf0e025e73261a8f56302e9b74d8a7b597df8bdef1ee4ce8503dfc4fc94be16b91227b358cba7c5bc1fabde182876f6becf7 linux-google-glass-1091b53a0b5e20d23a8447161e181e2a53e944de.tar.gz
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405) Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using aes-xts-plain64 as default cipher for cryptsetup (override with "pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940). I have executed "pmbootstrap kconfig edit" on each kernel, and manually toggled the option. The diff is not always clean, because for some kernels it is apparently the first time, that menuconfig was executed on the configs like that. In a few instances, it turned out that CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is already a requirement, but as the config was incomplete, it was not visible that this option was enabled). Very few times, I had to enable CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS. It would be great if we could automate such mass kconfig edits in the future, see pmbootstrap#1942. [skip ci]: I have verified, that every single one of these kernels builds. CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
0f37a7112c45893ba431f3f0051fa99b4b9c1ed59c62b165a5edb7d80b114d1f73bde06fdbb6be972bef6ddb51933bb8e5862a0e7b55c4552f3301c62bff9f88 config-google-glass.armhf
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"
Reference in a new issue Copy permalink