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

60 lines
2.6 KiB
Text
Raw Normal View History

New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
# Kernel config based on: arch/arm/configs/bcm21664_hawaii_ss_kylevess_rev00_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-samsung-kylevess
New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
pkgver=3.4.5
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=9
New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
pkgdesc="Samsung Trend Lite kernel fork"
arch="armhf"
_carch="arm"
_flavor="samsung-kylevess"
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 xz 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: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
# Source
_repository="kernel_samsung_kylevess_f2fs"
_commit="17667b5c69eaf3db40ca2040d965d14cfd09a427"
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: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +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/opensource591/$_repository/archive/$_commit.tar.gz
New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
$_config
00_return_address.patch
01_patch_lifebook_detect.patch
02_patch_fsp_detect.patch
03_fix_to_state.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
New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +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: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +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: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +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: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
}
sha512sums="ef1881e26be013a4f58eac86c884b3f2d50e7b742e97d7655832865089a4776e83b19df64ecda332a4cb44c5ce8006679428b22248590be881948821c45f469f linux-samsung-kylevess-17667b5c69eaf3db40ca2040d965d14cfd09a427.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
60a2c4342441d986d2545418f52f12b66578ca0ef1a55957ce282bd432fce2b5537a53b836cce369e792a4f3cd4acce5f081de948046156e7754a21134c122a1 config-samsung-kylevess.armhf
New device: samsung-kylevess (Galaxy Trend Lite, s7390g) (#1541)
2018-06-10 14:20:36 +00:00
c40eaa11547f5bc2b1ff965506bdfe3015ff16e4b5ad9ccb3b8134ceafd1d32407c4ef2b213e02e036ce1e9bdcbfe768dff7d4b054bec77705a176c1f783b6f5 00_return_address.patch
36418ec3d31d1d6d9915afcf3d38d4549aeeb49c3825414b51b67db7a1ab6482f22d2723da3b258b671956809949278a51f6507df9b0052aec0bd0c59f56919a 01_patch_lifebook_detect.patch
9da951bb0391564f33bdb0a97c339997eda7b15ec2f160da8af237cc87c233b8c3dcdc1a12759e04d69d075ae9b0afaf726101ef356e788d7f4606a03db2e248 02_patch_fsp_detect.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
7bc5894a412d45e45e308915dbe3a964419f443f149ef390d2f09151dd15ca86767c7fdd4e927cfb602d6d455755d4941d68a9f139a1cd3f89f0d90088dafde4 03_fix_to_state.patch
2b48f1bf0e3f70703d2cdafc47d5e615cc7c56c70bec56b2e3297d3fa4a7a1321d649a8679614553dde8fe52ff1051dae38d5990e3744c9ca986d92187dcdbeb gcc10-extern_YYLOC_global_declaration.patch"
Reference in a new issue Copy permalink