forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/archived/linux-htc-flounder-downstream/APKBUILD

62 lines
2.7 KiB
Text
Raw Normal View History

device: rename unmaintained to archived (MR 5046) Unmaintained is a name which on multiple occasions have seen lead to confusion with people having the impression that unmaintained is for all unmaintained devices, which is not how we're really using it. Many devices in testing do not actually have a maintainer, yet there has been no push to move these out of there and into unmaintained. I think this is a result of that unmaintained was introduced not to keep unmaintained ports but rather a place to store ports that have a better replacement but where the inferior one still holds some sort of value, such as for debugging purposes. These ports also are not necessarily entirely unmaintained and see more fixes than many ports in testing. While one approach to solving this problem could be to simply moving all unmaintained ports to unmaintained, I think this comes with some problems: It would require an initial effort to figure out which ports are indeed unmaintained and which just don't have a maintained noted in the package, and given how many ports there are in testing this would be a big endeavour. It would also require continuous work on moving ports into unmaintained as the maintainers go silent if we are to keep testing and unmaintained's state consistent with reality. Additionally, just because a port doesn't have a maintainer on paper doens't mean that there aren't people who aren't willing to fix it up if there are issues that arise. As such, I think the way to go is renaming unmaintained to better reflect the original intent. Thanks to Luca Weiss for suggesting "archive", and to Arnav Singh for suggesting that "archived" would match the other category names better.
2024-04-18 17:19:42 +00:00
# Archived: Downstream port, only for testing. Use mainline port (htc-flounder)!
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
# Kernel config based on: arch/arm64/configs/lineage_flounder_defconfig
htc-flounder: move downstream pieces to unmaintained (MR 3623) It can still be chosen as 'htc-flounder-downstream' in pmbootstrap init.
2022-11-07 10:45:44 +00:00
pkgname=linux-htc-flounder-downstream
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
pkgver=3.10.103
linux-htc-flounder-downstream: fix build (MR 5112) Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401 [ci:skip-build]: already built successfully in CI
2024-05-06 20:39:11 +00:00
pkgrel=1
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
pkgdesc="Google Nexus 9 kernel fork"
arch="aarch64"
_carch="arm64"
htc-flounder: move downstream pieces to unmaintained (MR 3623) It can still be chosen as 'htc-flounder-downstream' in pmbootstrap init.
2022-11-07 10:45:44 +00:00
_flavor="htc-flounder-downstream"
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
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: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
# Source
_repository="android_kernel_htc_flounder"
_commit="a8f66d78789d66906c886fd6818fb648d0a84a2a"
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: htc-flounder (#1309)
2018-04-04 00:27:11 +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
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +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
linux-htc-flounder-downstream: fix build (MR 5112) Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401 [ci:skip-build]: already built successfully in CI
2024-05-06 20:39:11 +00:00
linux3.4-ARM-8933-1-replace-Sun-Solaris-style-flag-on-section.patch
linux3.4-fix-piggy.gzip.S.patch
linux3.7to4.5-ARM64-remove-Sun-Solaris-style-flag-on-section.patch
New device: htc-flounder (#1309)
2018-04-04 00:27:11 +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: htc-flounder (#1309)
2018-04-04 00:27:11 +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: htc-flounder (#1309)
2018-04-04 00:27:11 +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: htc-flounder (#1309)
2018-04-04 00:27:11 +00:00
}
linux-htc-flounder-downstream: fix build (MR 5112) Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401 [ci:skip-build]: already built successfully in CI
2024-05-06 20:39:11 +00:00
sha512sums="
b9ee4b14b0466e0b19d869810ceb852dd70399a90cdb081b902177685b87d242e11284bb0f619ea103b30ef5544f06a88c0131d028024ad8aa45809697e070fa linux-htc-flounder-downstream-a8f66d78789d66906c886fd6818fb648d0a84a2a.tar.gz
htc-flounder: move downstream pieces to unmaintained (MR 3623) It can still be chosen as 'htc-flounder-downstream' in pmbootstrap init.
2022-11-07 10:45:44 +00:00
1843a10732e6d21379993aa3b3ca24040d7f11de2bf9959056a39976dc5e7f4ec6a743c6a36120d72a6614a242c0159ce31efe3f1d15cc284eb355cd1c82f9ef config-htc-flounder-downstream.aarch64
linux-htc-flounder-downstream: fix build (MR 5112) Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401 [ci:skip-build]: already built successfully in CI
2024-05-06 20:39:11 +00:00
2b48f1bf0e3f70703d2cdafc47d5e615cc7c56c70bec56b2e3297d3fa4a7a1321d649a8679614553dde8fe52ff1051dae38d5990e3744c9ca986d92187dcdbeb gcc10-extern_YYLOC_global_declaration.patch
9e3b067fa1b19ad02500c4fce1b6142051df3845c508e615788beb650c4f953683107ac2d80670c4e3df38f532e0e91060d2d13ec04c9ec985abd2dfa82e900b linux3.4-ARM-8933-1-replace-Sun-Solaris-style-flag-on-section.patch
080745ca4ecaa804ee1df26ea81975ca93b74372e0c08322a6c481e97807495ae6ceb6cc77653afa24f9f2df45da8ebf8e5de6b06037fbb08e0279877ce42188 linux3.4-fix-piggy.gzip.S.patch
75545ccd0082a119b9ad95fcef3523c939a5c946f8f3a5c3dde15cee1502f6c1011050a0ad5359426f018bb7ceea1c97a28c7665941bc89f365c8d11065ce0f6 linux3.7to4.5-ARM64-remove-Sun-Solaris-style-flag-on-section.patch
"
Reference in a new issue Copy permalink