Yep, I've reproduced this on minimal installs of both ArchLinux and Ubuntu.
`apt install fontconfig` fixes it on Ubuntu. On Arch, I had to install
fontconfig and a font (I tried ttf-droid) before it started working.
- Dan
On Sat, Nov 23, 2019 at 7:41 PM Daniel Fullmer wrote:
> I believe I've
I believe I've encountered this error in the past. I was able to work around
this by installing freetype / fontconfig (can't recall if one or both are
necessary).
On Saturday, November 23, 2019 at 9:15:36 PM UTC-5, Brian Moore wrote:
>
>
> I've been building AOSP for my pixel devices for a few
That's strange, I've got no idea why you're hitting it, but that we haven't
seen it anywhere else.
I've filed https://issuetracker.google.com/145064117 with my findings so
far.
- Dan
On Sat, Nov 23, 2019 at 6:15 PM Brian Moore wrote:
>
> I've been building AOSP for my pixel devices for a few
If you're trying to build android 10 (and not master), your best bet would
be to run a VM with Linux in order to build -- it very well may be a faster
build, and it will be a lot closer to what actually ships. The Mac build
works well enough for development, but it's not as complete as the Linux
I've been building AOSP for my pixel devices for a few versions now, but
I'm running into an issue in the release of Android 10.
I'm working with 10.0.0 r10, building for Pixel 3 (blueline).
I have the Google and QCom vendor binaries in the vendor/ tree, just as
I've always done.
I do a normal
No moved back to Mojave . MAC OSX 10.14
I think those errors has to do with Python compatibility issue or
libsepolwrap.dylib conflict with Catalina
Please let me know if you fix this. I am curious to know
- Dhanyu
On Fri, Nov 22, 2019 at 7:11 AM Jianwu Gao wrote:
> Hi
> I got same
