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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 11E66138359 for ; Fri, 24 Jul 2020 18:12:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 21DDBE0830; Fri, 24 Jul 2020 18:12:54 +0000 (UTC) Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 17944E0830 for ; Fri, 24 Jul 2020 18:12:53 +0000 (UTC) Received: by mail-pj1-x1035.google.com with SMTP id f16so5769242pjt.0 for ; Fri, 24 Jul 2020 11:12:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=F53+++LSlP7SKRPIXoVC2A/bG3MOYUtbRHleVOQojHU=; b=CYcFZLhy5R7p9plr2D9q/B3NDUiexKLIJgN/Jt4AFYxhsSOjEycaNz1nUYqsmkfuwT Nv9ui9GQUFvpQkGqGw/5fGwSqs7BFQisquXS4j7JDM7PGk2QY5pAcD2+w+5fNc0wGAe3 qGt4w2Q//+81PZNBgeO/MIi1NwH99AryfnfHtnHRbVnOmPu25xkk70v2TzTk8u/nFCEj WnwAemrvbO0lo5zWKWeYSHEmg1UBOnCy6ysE6VZYZl8NmJPYH9w88Hj/7yuq/54n/wCY BYXYOEad+FewZGTW5sCEAcfdAbioxHIlppLxuoEgkfRR2bG8pJSffOs4laTiYb5prqsH vY0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=F53+++LSlP7SKRPIXoVC2A/bG3MOYUtbRHleVOQojHU=; b=in5nLIzAobgmVeQq3QPfUqBGc8r56tSv+Gr6iQw0I4HXztzfozARua+imy25hgXnOq qPu2XxFavLWWUPHhrOWd/I/I//+FNzNePhVxeiXe76xIXIYfGEksVzofEq/MuNzSWhts IwgB33a9C2CS7Htt2FbdR0TNBLhgna8guSWzhnQGvW9GyAjlj7aPHelnZ3V205IenwId 2xl2aGS2PQDzVas8GwFqV+8vnfnBZD81Tp82kbv96tRY0LI8ErqEl+kyes79V8HBN3eu suTIHRdTelBk9ndRvekj5SpncO2SvDv6Gqdg7uJ6gjBfc3XZgd+LbCpnpZ9qoIz9KB2h pCEg== X-Gm-Message-State: AOAM5337LNEdI8hcG/76daifL0DowMUekjtmvBpYQ9rfS2bW1y1JsnHP NNCvdf7AlmLs34w0rGxIMEXIn9gm X-Google-Smtp-Source: ABdhPJxNcN9EzrdbOuuJo/9aXXYF4CfFYDqaQ62Fz5Zqmja+7hrsyBaYYBdJ1ISOqxNbBSAjrEQ8sQ== X-Received: by 2002:a17:90a:db48:: with SMTP id u8mr6126801pjx.169.1595614372756; Fri, 24 Jul 2020 11:12:52 -0700 (PDT) Received: from localhost ([106.215.5.42]) by smtp.gmail.com with ESMTPSA id x10sm7193441pfp.144.2020.07.24.11.12.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jul 2020 11:12:51 -0700 (PDT) Date: Fri, 24 Jul 2020 23:42:48 +0530 From: Gunwant Jain To: UnderSampled Cc: gentoo-soc@lists.gentoo.org Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android Message-ID: <20200724181248.vq2pend65raptjvw@tardis.localdomain> References: <20200720074024.ayyqx5dk5hrngn7m@tardis.localdomain> <877dutngy8.fsf@robot.e.airelinux.org> <20200724150257.sngrh6wxazjxpggo@tardis.localdomain> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2wgjoirs7kma7okx" Content-Disposition: inline In-Reply-To: X-Archives-Salt: 55ba511c-dc50-49c2-a5c0-7ca993968838 X-Archives-Hash: 18487912549a81f4e2d06351dce0ea02 --2wgjoirs7kma7okx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey Stephen, I took a brief look at GloDroid. It looks like just another AOSP tree but with support for more devices like you mentioned.=20 But SharkBait aims to build Android on the device itself, the flavour of Android should not matter. And for the same reasons, I chose Lineage's tree because of the massive device support it has. To implement SharkBait, we will have to swap the toolchains AOSP offers=20 with the ones supporting aarch64 host. Once that is sorted out, we could, in theory, implement any flavour of AOSP, be it glodroid, or any other fork, just by tracking SharkBait's toolchain sources. On top of that SharkBait aims also to separate the AOSP modules and provide updates via Portage. But I predict that this would be SharkBait specific. Targeting newer devices like the PinePhone would be like the normal way AOSP forks like Lineage extend support to newer devices. I agree on a PinePhone target. Once again, I thank you for offering me help in getting such devices. But I would politely ask for you to wait until I implement SharkBait on a phone first (the Lineage sources for my phone are easily available). Benda offered me an arm64 server for the project, I think that would be enough to work on, once I succeed in building the toolchain (or fail to do so because of hardware limitations). Thanks, Gunwant On 20/07/24 01:07PM, UnderSampled wrote: > You may find this useful: https://glodroid.github.io/ > This is a modern AOSP tree for OrangePi, RaspberryPi, and Pine64 devices.= That includes the Pinebook and PinePhone: https://www.pine64.org/. >=20 > I can get you one of these devices if you think it could help. >=20 > We should definitely consider targeting a build of Shark Bait for the Pin= ePhone. >=20 >=20 > On July 24, 2020 11:02:57 AM EDT, Gunwant Jain = wrote: > >On 20/07/24 10:08PM, Benda Xu wrote: > >> Gunwant Jain writes: > >>=20 > >> > This week, I started managing the structure for the modified > >LineageOS > >> > fork we would keep. Namely the modified `repo-manifest` [1] and > >> > `llvm_android` [2], for now. No patches have been applied to them > >yet > >> > for the reasons discussed below. > >> > > >> > My plan for this week was to start with patching the `llvm_android` > >> > build scripts. Android uses a prebuilt Clang (bundled with the > >repo) > >> > among other stuff to build the toolchain. So I had to emerge Clang > >on my > >> > phone. > >> > Emerging Clang turned out not to be a breeze when I have a phone > >with 3 > >> > gigs of RAM. So for about the longest time, I was busy trying to > >make up > >> > for it. I tried setting up distcc, increased swap/zram, but still > >the > >> > OOM killer got me. > >> > Later last night(/day), I came across the tips for building > >clang/gcc in > >> > an embedded Android environment at [3]. So I followed that and as > >of > >> > now, me writing the mail, OOM has not got me, Clang is emerging. > >>=20 > >> Did it finally go through? > > > >Yes it did. > >I can also report that llvm_android's stage1 clang is compiled for > >aarch64, I am on the stage2 step currently. > > > > > >Regards, > >Gunwant >=20 > --=20 > Sent from my Android device with K-9 Mail. Please excuse my brevity. --2wgjoirs7kma7okx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEVcYcuddz0Grkn4q20gpuZPFudnkFAl8bJKAACgkQ0gpuZPFu dnku9Af9Eee2pb3DdaqS1R/z7kUmtdcXjA4am3ehl5JevEZaDP6L00sdBul25qlh zU7Rwg3FvTBuqzX3Kdlxy316bOezMJU6hLmF+oet9OTIIKAEHh7KchQEm33YgrND 2Sii1Yy7xKSEvba2rCh5MR8or8ElhvnBuQMKSd+6rn5hslB1shxxsxFxEnJn9W1i oIRSx1NHQj0da7CN434yUU08Kz9oP6pWEVkbpmxxPdEdIjWwmpEo/bru5bVZiPOl +rbBi9qleEe6P0gZCcGw0aakwSt582/9VtgtncvY7qDseAZXRs3fVp/lo4koM80Q cHYlEx2yeApyt6gWOzF/hbmFfFu/hg== =B5IH -----END PGP SIGNATURE----- --2wgjoirs7kma7okx--