From: UnderSampled <undersampled@live.com>
To: gentoo-soc@lists.gentoo.org,Gunwant Jain <therealgunwant@gmail.com>
Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android
Date: Fri, 24 Jul 2020 13:07:33 -0400 [thread overview]
Message-ID: <BN6PR03MB3378ECB32D734225A5619228A9770@BN6PR03MB3378.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20200724150257.sngrh6wxazjxpggo@tardis.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
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/.
I can get you one of these devices if you think it could help.
We should definitely consider targeting a build of Shark Bait for the PinePhone.
On July 24, 2020 11:02:57 AM EDT, Gunwant Jain <therealgunwant@gmail.com> wrote:
>On 20/07/24 10:08PM, Benda Xu wrote:
>> Gunwant Jain <therealgunwant@gmail.com> writes:
>>
>> > 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.
>>
>> 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
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 2450 bytes --]
next prev parent reply other threads:[~2020-07-24 17:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 7:40 [gentoo-soc] Weekly Report: Portage Powered Android Gunwant Jain
2020-07-24 14:08 ` Benda Xu
2020-07-24 15:02 ` Gunwant Jain
2020-07-24 17:07 ` UnderSampled [this message]
2020-07-24 18:12 ` Gunwant Jain
2020-07-25 3:00 ` Benda Xu
2020-07-25 8:02 ` Gunwant Jain
2020-07-25 8:21 ` Gunwant Jain
-- strict thread matches above, loose matches on Subject: below --
2020-08-17 18:05 Gunwant Jain
2020-08-17 23:15 ` Benda Xu
2020-08-20 6:21 ` Gunwant Jain
2020-08-12 1:41 Gunwant Jain
2020-08-12 7:34 ` EBo
2020-08-14 7:26 ` Gunwant Jain
2020-07-30 15:00 Gunwant Jain
2020-07-13 23:09 Gunwant Jain
2020-07-14 0:17 ` Benda Xu
2020-07-14 5:01 ` Gunwant Jain
2020-07-15 1:04 ` Benda Xu
2020-07-15 1:09 ` UnderSampled
2020-07-15 4:55 ` Gunwant Jain
2020-07-15 4:45 ` Pengcheng Xu
2020-07-15 4:58 ` Gunwant Jain
2020-07-15 4:52 ` Gunwant Jain
2020-07-14 4:05 ` Pengcheng Xu
2020-07-14 5:05 ` Gunwant Jain
2020-07-08 11:39 Gunwant Jain
2020-07-08 13:53 ` Pengcheng Xu
2020-07-09 1:04 ` Benda Xu
2020-06-29 20:12 Gunwant Jain
2020-06-29 21:27 ` EBo
2020-06-30 21:42 ` Gunwant Jain
2020-07-01 2:37 ` EBo
2020-07-01 3:15 ` Gunwant Jain
2020-07-01 12:40 ` Lucas Ramage
2020-07-01 7:17 ` Benda Xu
2020-07-01 16:12 ` Gunwant Jain
2020-07-01 14:07 ` Pengcheng Xu
2020-07-01 16:53 ` Gunwant Jain
2020-07-02 3:50 ` UnderSampled
2020-07-02 12:14 ` Gunwant Jain
2020-06-22 19:15 Gunwant Jain
2020-06-23 4:45 ` Pengcheng Xu
2020-06-23 11:44 ` Gunwant Jain
2020-07-01 7:14 ` Benda Xu
2020-06-15 8:03 Gunwant Jain
2020-07-01 7:10 ` Benda Xu
2020-06-09 11:39 Gunwant Jain
2020-07-01 7:08 ` Benda Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN6PR03MB3378ECB32D734225A5619228A9770@BN6PR03MB3378.namprd03.prod.outlook.com \
--to=undersampled@live.com \
--cc=gentoo-soc@lists.gentoo.org \
--cc=therealgunwant@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox