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