This BINHOST collection is things I've built over the years for my own use. It seems a shame to lose it and I might need it again too. If you are looking for newer versions or packages that are not here ping me on IRC. Its updated frequently. If you have a different ARM cortex-a53 (Pi 3) or a ARM cortex-a72 (Pi 4) platform you may find this binhost useful. It all WorksForMe. If its useful to you, you are welcome. ### WARNING WARNING WARNING WARNING WARNIRNG WARNING #### Everything here is built with the /17.0/ profile. The /23.0/ profiles introduce some hardening changes When /23.0/ packages are added it is important to choose the profile matching your install ### WARNING WARNING WARNING WARNING WARNIRNG WARNING #### Now Split for /17.0/ and /23.0/ profiles. The /17.0/ profile BINHOSTS will only be maintained sporadiclly. The /23.0/ profile is stable now, so you should switch. --------------------- 17.0/gcc-13.x -------------------------------- ------------- Use this one - Unless its for a Pi 5 ---------------- Pi 5 users skip to the bottom. The gcc-13.x binhost started out from the weekly masked gcc-13 snapshot. Now that gcc-13 is ~arch the gcc-12 binhost will only be maintained irregularly, or maybe not at all. It has all been Hawk built. So it's Fully 64 bit Pi compatible. https://wiki.gentoo.org/wiki/Gentoo_on_Hawk The Hawk CPU +cryto is off in the KVM as the Pis are missing the crypto extensions. The code should be run time compatible with gcc versions back to gcc-6 so mix and match should be safe. The build server ran out of HDD space so old binpackages with ebuilds not in the tree as of Sat Nov 11 10:10:23 AM UTC 2023 have been ecleaned. That freed about 35G. The sources are still available and the ebuilds are in git, so the old packages can be recreated. -------------------- 17.0/gcc-12.x -------------------------------- -------------------- Abandoned ------------------------------ Thet last planned update was 06-Jun-23, that included the python3_11 update to make it easy to pick op the pieces in case I ever need to. The KVM was removed to clone 17.0/gcc-13.x to make 23.0/gcc-13.x It has all been hawk built. So it's Fully 64 bit Pi compatible. The Hawk CPU +cryto is off in the KVM as the Pis are missing the crypto extensions. The code should be run time compatible with gcc versions back to gcc-6 so mix and match should be safe. The Hawk is essentially an X-Gene 3 CPU, which is like four X-Gene 1 CPUs in the same package with some minor tuning. --------------- 17.0/gcc-10.x and 17.0/gcc-11.x ------------------- -------------------- Both abandoned ------------------------ Will be going away soon as I don't have the KVM to build with these versions of gcc any more. The gcc-10.x built arm64 binhost here is made on a Mudan arm64 server. https://wiki.gentoo.org/wiki/Gentoo_On_X-Gene_1_Mudan It has an X-Gene 1, 8 core CPU at 2.5GHz, with very little cache and 128G RAM. The gcc-11.x built arm64 binhost is mostly made on the Mudan arm64 server above but I have recently migrated it to a Hawk, which can trace its roots to an X-Gene 3, 32 core CPU at 3.0GHz The directory etc_portage_X-Gene is the /etc/portage used to build the binhost. The X-Gene 1 CPUs' main claim to fame is that it was the first arm64 CPU and is the only arm64 CPU that does not have the CRC extensions. CFLAGS are still set to optimise for the Pi 4 in 64 bit mode. It also works on Pi3 and an Acer R13 Chromebook. Only one pacage has been built without +crc so far. The idea is not to run the packages on the X-Gene, only build them. The binaries are installed on my Pi 4. -------------------- Pi 5 17.0/gcc-13.x -------------------------- Abandoned but use it while its useful to you. The Pi5 is testing the /23.0/ migration The Pi5 is a cortex-a76 CPU which is armv8.2a with bells and whistles. The Hawk is only armv8a. That means that while it can build RPi 5 code, it may not be able te execute it. gcc is a good example. The stage 2 build generates an Illegal Instruction error. Hmm buildpkgonly ... thats worth a look for some packages. gcc will still fail. Packages that need to run on the Hawk cannot be built for the Pi 5 there are will not be included in the binhost unless they are built on a real cortex-a76 CPU. The path af least resistance is to build on the Pi5 for now. The Pi5 binhost as been built that way entirely. Other options, like cross compiling, are being explored. -------------------- Pi 5 23.0/gcc-13.x -------------------------- Built with the arm64/23.0 profile plus -mbranch-protection=standard which is expected to go into the profile before its released for ~amd64 testing.