Meanwhile, as my phasing out of using GitLab SaaS continues, I'll remove all GitLab mirrors, except for prebuilts; they will only be available from GitHub, as I plan to instead reduce namespace usage as much as possible.

Not the usual context but help needed for commit description of https://github.com/krasCGQ/build-tools-gcc/commit/ea9b8cedf2303569a9b7ece9541fd90e1d6456de

I missed the announcement of .327 being merged for two days, meanwhile...

ugglite returns to roster after I managed to get a new, but aftermarket, battery offline.

This was unrelated in any part to KudProject since I refuse to acknowledge to, but I'll announce it either way in this channel since I have nowhere else to announce.

If you remember about the build-tools-gcc script which was written in part to provide toolchain for Linux-targeting machines that is built with latest components available, I wasted nearly a month to try to get all available GCC versions offered by the script to build and here we are!

The latest build script (on dev branch) can now build GCC toolchains from 4.9 to 12 for ALL architectures and less hacks needed (except on a few target combinations).

CLooG fetching was added to the build script as it's required to get GCC 4.9 and below to have graphite loop optimization support. This has no effect on later versions as they aren't required.

GCC 10 and above toolchains will be built with latest libzstd which will also be fetched by the build script so that it can stop depend on system one which is almost certainly be older especially on LTS distro. libzstd is required for Zstd compression support of LTO bytecode, although overall not required to generate a working GCC.

A number of behavior fixes as well as adjustments to build steps are also included so we can stop depending on some nasty hacks we previously had.

Debian 10 (Buster) is now recommended to utilize the build script with soon-to-be EOL Ubuntu 18.04 LTS as the minimum requirements.

That's all changes for the time being so I can stop stalling any other projects for even longer time than it'd have deserved.

Enjoy!

Oh well, if all you need is some bare-metal targeting toolchain, I won't be supporting it in the build script, because some simpler ones like this will suffice.

Using newlib for the libc will be more useful, though.

v4.9.329 has been merged.

v4.9.330 has been merged too.

No new kernel merges this week, but Pronto/Prima and CLD3 WLAN modules have been updated to latest version available.

v4.9.331 has been merged into msm-4.9 kernel fork; announcement is late as testing was done while I'm doing some phone repairs

I guess people reacting with angry emojis have mental problems

No order will be specified, neither priority, these are just planned ones:

Samsung Galaxy S4 GT-I9500 (ja3gxx) - Android 7.1.2 (in progress)
Xiaomi Redmi 3 (ido) - Android 11
Xiaomi Redmi Note 5A (ulysse) - Android 12L?
Asus ZenFone Max Pro M1 (X00T) - Android 13?
Xiaomi Mi 9 SE (grus) - Android 12L? 13
Xiaomi Redmi Note 8 (ginkgo) - Android 13?
Redmi K40 / POCO F3 (alioth) - Android 13 / SnuggyWuggy

Uh well, to be honest, I'll probably have to invest in some bigger SSDs since investing in doing 4 different Android versions will starve so much space on my already congested 1.5 TB combined storage of my PC

Back then I managed to get a Galaxy A20 abandoned by my brother a year ago fixed, but he decided to not use it anymore out of concern that it might be too laggy, so I can probably add Galaxy A20 (a20) to the planned build roster as well, since Samsung's warranty has expired either way

Edit: Redmi Note 4 (mido) remains out of order

Uh well, I guess he's going to use it again afterall...

Some updates for this:
A number of patches from LAW.BR.4.0-48500-89xx.0 have been merged into msm-4.9 kernel fork rather than merging the tag; this is meant to avoid unnecessary merge conflicts that might appear in the future due to how much Frankenstein this tree has nowadays.

1.37 AM edit: force pushed back to state it was on 27 October, you all are invited to test changes I mentioned by merging a11/upstream-caf branch, that remains for now since it has probability to break msm8953 platform devices in general especially audio.

Update over this, is that they have been pushed once again. The only highlights is just that the kernel fork now has full sdm429w/spyro support (yes, WearOS), and it shouldn't affect any other msm8953 platform.

msm8953-based devices that use digital codec rather than internal codec may also benefit from this merged patchset.

All unmerged security patch backports until topic:n-asb-2022-11 have been merged into n branches.


Edit:
Note that I'm merging the November topic earlier than I should have, that in case of patches that come up later after this will surely follow and be notified upon.