From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 74E3A158094 for ; Mon, 8 Aug 2022 11:18:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9E9DDE0BDF; Mon, 8 Aug 2022 11:18:18 +0000 (UTC) Received: from raba.swcp.com (raba2.swcp.com [216.184.2.223]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 50138E0BDF for ; Mon, 8 Aug 2022 11:18:17 +0000 (UTC) Received: from roundcube.swcp.com (roundcube.swcp.com [216.184.2.221]) by raba.swcp.com (8.15.2/8.15.2/Debian-14~deb10u1) with ESMTP id 278BIA0h031390; Mon, 8 Aug 2022 05:18:11 -0600 Received: from roundcube.swcp.com (localhost [127.0.0.1]) by roundcube.swcp.com (8.15.2/8.15.2/Debian-8) with ESMTP id 278BIAg0014303; Mon, 8 Aug 2022 05:18:10 -0600 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Date: Mon, 08 Aug 2022 07:18:10 -0400 From: EBo To: gentoo-soc@lists.gentoo.org Cc: cat@catcream.org Subject: Re: [gentoo-soc] Gentoo musl Support Expansion for Qt/KDE Week 8 In-Reply-To: References: <182a47071dee4f163b82369253810c8d@sandien.com-N8urors----2> User-Agent: Roundcube Webmail/1.4.12 Message-ID: X-Sender: ebo@sandien.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: a826a52f-546f-4289-847d-6527a383f3a8 X-Archives-Hash: b33fc853da12b04c2f7723f992ea2ff5 When you get the draft of step-by-step doc, sit down and do a clean install and follow the step-by-step to verify that it works as documented. Maybe if you have someone that can beta test things, they can verify the final docs. Anyway, that is all I meant. EBo -- On Aug 8 2022 6:58 AM, cat@catcream.org wrote: > Yes! I have week 12 fully dedicated to writing documentation actually. > I have written some notes but I'll also use my daily blogs to remind > me of what to write about :) > > What do you mean by "and verification that they are really up to > date", like so the older docs are really up to date? For the PinePhone > Pro in particular I'd like to do something like this > https://wiki.gentoo.org/wiki/PinePhone but with a lot more > information. > > > > Aug 8, 2022, 02:33 by ebo@sandien.com: > >> I'm not one of your mentors (I am a former GSOC intern and mentor; >> which explains why I am still on the lists). >> >> All of this sounds like wonderful progress. The one thing I have not >> seen you mention is documentation, quick-starts, and verification that >> they are really up to date. Spending a week or two on those to polish >> then up would be a wonderful addition. >> >> EBo -- >> >> On Aug 7 2022 8:01 PM, cat@catcream.org wrote: >> >>> This week I've spent most of my time getting Gentoo musl to run on my >>> PinePhone Pro and packaging mauikit apps. I have also done some minor >>> testing on KDE applications and some other miscellaneous things. >>> >>> In my proposal I had initially planned on porting KDE applications >>> and >>> making them build on Gentoo musl the following two weeks, and then >>> making sure test suites run the week following that. But I've already >>> gotten kde-apps-meta installed and the programs are working well for >>> the most part. Though I haven't enabled every use flag for the KDE >>> apps and I haven't ran every test suite so there's definitely work to >>> do left, just not 3 weeks work. So instead I asked Sam if I could >>> spend some time working on getting Gentoo musl to run on my PinePhone >>> Pro with Plasma Mobile as a side project. >>> >>> >>> Starting with the PinePhone. The Gentoo install itself was pretty >>> smooth and I didn't run into any major issues. But I really got stuck >>> on some other more low level and non-Gentoo bits. >>> The first issue I ran into was when I installed a new kernel onto it. >>> Apparently a single developer called Megi does most of the PPP kernel >>> development so I installed his kernel. Confusingly his development >>> branch is called "orange-pi-5.x" and it took me some time figuring >>> that out :D. Anyways, the compilation itself was straight forward, >>> and >>> the defconfig _almost_ worked well. I stole the bootloader >>> configuration from PostmarketOS, rsync:ed the kernel + dtbs, and then >>> changed some relevant parts in the bootloader config. Sadly the phone >>> did not boot, and there was no output to be seen on the screen :/. >>> After reading the wiki I found out that I could connect via serial >>> through the headphone jack. I used an RS232-to-USB adapter and >>> soldered it onto the internal wires of a 3.5mm cable. For output this >>> did work, but when connecting TX to also get input, the output just >>> got messed up and I couldn't read it. I tried to debug this and also >>> seeked help from others, but ultimately couldn't get it to work. >>> Luckily the only thing I needed was output because I saw in the >>> bootlog that EFI stub was missing from the kernel. Enabling that and >>> generating an initramfs made the phone boot! >>> >>> Then I started emerging some packages, and even though I had the >>> charger plugged in, the phone completely discharged after a while. >>> After that the phone did not want to boot and I tried all kinds of >>> things, like booting from SD card, reflashing bootloader, trying >>> different cables and nothing worked ... It turned out that the >>> bootloader (Tow-boot) had a bug that made the phone not charge after >>> the battery as emptied, and I needed to boot it into a special mode >>> holding a button with a sim card opener. >>> >>> After that I set up distcc with cross compilation, and there came the >>> second issue. "__aarch64_cas4_sync undefined symbol". I asked Sam and >>> he said it probably was a distcc issue. Because of me not wanting to >>> run into this again I tried the aarch64-gentoo-linux-musl-emerge >>> wrapper instead. This worked for the most part, but I had trouble >>> with >>> copying over my phones configuration to /usr/.../etc/portage. >>> I then learned about the ROOT, SYSROOT, and PORTAGE_CONFIGROOT >>> variables. Toghether with sshfs I could easily emerge packages for >>> the >>> phone on my PC without using something slow like qemu-user, nice! >>> I emerged a lot of packages like this and noticed that the program >>> dispatch-conf did not honour the variables. This was easy to fix and >>> I >>> PR:ed it here https://github.com/gentoo/portage/pull/881. >>> >>> I have also created a lot of ebuilds for Mauikit apps, these are >>> cross >>> platform KDE applications that look great on smaller devices like >>> phones. https://github.com/gentoo/kde/pull/910/commits. They also >>> work >>> great on my PC. >>> >>> All in all I've spent most my time this week working on the >>> PinePhone, >>> and the two following weeks I'll do a lot of testing for the KDE >>> applications. >>>