Re: [android-building] Re: Dex2oat failed to compile a boot image

['Dan Willemsen' via Android Building]

As posted with the announcement:

This preview is not a full platform update and only for reference.


I would not expect this to build or necessarily get any further (eg
boot/etc). Only some components have been updated, and that's done on a
git-project boundary, so the entire build graph gets skewed significantly
between old and new projects.

- Dan

On Mon, Mar 30, 2020 at 10:10 PM Guoyin Chen  wrote:

> There are quite a lot of build error with android-preview-2 build. I think
> google have several wrong tag on different gits.
>
> On Tuesday, March 31, 2020 at 8:41:18 AM UTC+8, Michael Goffioul wrote:
>>
>> I found out I was missing this change:
>> https://android.googlesource.com/platform/libcore/+/271b4054b825efca3176c4ac11565e33cff5d09a
>> I cherry-picked it, but now I'm getting a different error:
>>
>> dex2oatd F 03-30 19:11:33  6962  6962 unstarted_runtime.cc:2085] Calling
>> native method void android.system.OsConstants.initConstants() in an
>> unstarted non-transactional runtime
>>
>>
>> On Mon, Mar 30, 2020 at 6:59 PM Michael Goffioul 
>> wrote:
>>
>>> On Mon, Mar 30, 2020 at 6:52 PM Michael Goffioul 
>>> wrote:
>>>
 I'm still experimenting with android-r-preview-2, and very close to the
 end of the build process, I'm getting the following error:

 FAILED:
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.vdex
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.vdex
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.vdex
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.vdex
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.vdex
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.art
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.invocation
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.oat
 out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.vdex
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
 out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot.oat
 dex2oatd F 03-30 18:38:12  5762  5762 class_linker.cc:8451] Check
 failed: previous_size == size (previous_size=108, size=104)
 Ljava/lang/DexCache;
 Runtime aborting...

 Any hint would be appreciated. I've never had that error in previous
 Android versions, I'm not sure what to look for.

 Note that the above error is accompanied with a message to add
 "--runtime-arg -verbose:verifier" to the

>>>
>>> My apologies, I hit send too early. I just meant to say the additional
>>> flag didn't provide more information.
>>>
>>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/494fa5bf-8949-4134-892f-efa17f4537ea%40googlegroups.com
> 

[android-building] Re: Dex2oat failed to compile a boot image

[Guoyin Chen]

There are quite a lot of build error with android-preview-2 build. I think 
google have several wrong tag on different gits. 

On Tuesday, March 31, 2020 at 8:41:18 AM UTC+8, Michael Goffioul wrote:
>
> I found out I was missing this change: 
> https://android.googlesource.com/platform/libcore/+/271b4054b825efca3176c4ac11565e33cff5d09a
> I cherry-picked it, but now I'm getting a different error:
>
> dex2oatd F 03-30 19:11:33  6962  6962 unstarted_runtime.cc:2085] Calling 
> native method void android.system.OsConstants.initConstants() in an 
> unstarted non-transactional runtime
>
>
> On Mon, Mar 30, 2020 at 6:59 PM Michael Goffioul  > wrote:
>
>> On Mon, Mar 30, 2020 at 6:52 PM Michael Goffioul > > wrote:
>>
>>> I'm still experimenting with android-r-preview-2, and very close to the 
>>> end of the build process, I'm getting the following error:
>>>
>>> FAILED: 
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.art
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.vdex
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.art
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.vdex
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.art
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.vdex
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.art
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.vdex
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.art
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.vdex
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.art 
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.invocation
>>>  
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.oat 
>>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.vdex
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>>>  
>>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot.oat
>>> dex2oatd F 03-30 18:38:12  5762  5762 class_linker.cc:8451] Check 
>>> failed: previous_size == size (previous_size=108, size=104) 
>>> Ljava/lang/DexCache;
>>> Runtime aborting...
>>>
>>> Any hint would be appreciated. I've never had that error in previous 
>>> Android versions, I'm not sure what to look for.
>>>
>>> Note that the above error is accompanied with a message to add 
>>> "--runtime-arg -verbose:verifier" to the 
>>>
>>
>> My apologies, I hit send too early. I just meant to say the additional 
>> flag didn't provide more information.
>>
>>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/494fa5bf-8949-4134-892f-efa17f4537ea%40googlegroups.com.

Re: [android-building] Re: Error running local cuttlefish instance

[Dean Wheatley]

After rebooting, acloud local is working! Thank you Kevin for your help.

run_cvd E 03-31 13:33:23  7602  7602 users.cpp:48] Group virtaccess does 
not exist
run_cvd I 03-31 13:33:23  7602  7602 main.cc:367] The following files 
contain useful debugging information:
run_cvd I 03-31 13:33:23  7602  7602 main.cc:369]   Launcher log: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/launcher.log
run_cvd I 03-31 13:33:23  7602  7602 main.cc:371]   Android's logcat 
output: /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/logcat
run_cvd I 03-31 13:33:23  7602  7602 main.cc:372]   Kernel log: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/kernel.log
run_cvd I 03-31 13:33:23  7602  7602 main.cc:373]   Instance configuration: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/cuttlefish_config.json
run_cvd I 03-31 13:33:23  7602  7602 main.cc:374]   Instance environment: 
/tmp/acloud_cvd_temp/local-instance-1/.cuttlefish.sh
run_cvd I 03-31 13:33:23  7602  7602 main.cc:375] To access the console 
run: socat file:$(tty),raw,echo=0 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/console
run_cvd I 03-31 13:33:55  7602  7602 main.cc:191] Virtual device booted 
successfully
run_cvd I 03-31 13:33:55  7602  7602 main.cc:198] 
VIRTUAL_DEVICE_BOOT_COMPLETED
launch_cvd I 03-31 13:33:55  7552  7552 launch_cvd.cc:211] run_cvd exited 
successfully.
OK! (33s)
Remote terminal can't support VNC. Skipping VNC startup.
Total time:  (33s)


Device summary:
 - device serial: 127.0.0.1:6520 (local-instance-1[127.0.0.1:6520])
   export ANDROID_SERIAL=127.0.0.1:6520

On Tuesday, March 31, 2020 at 3:51:39 AM UTC+11, Kevin Cheng wrote:
>
> We've seen the permissions errors go away after a reboot, have you reboot 
> your host after running `acloud setup --host`?
>
> On Mon, Mar 30, 2020 at 7:58 AM Dean Wheatley  > wrote:
>
>> Hi Kevin, the specific "acloud setup --host" is fixed.
>>
>> However, "acloud create --local-image --local-instance" is failing:
>>
>> $ acloud create --local-image --local-instance
>> ...
>>
>> launch_cvd I 03-30 15:12:18 2529578 2529578 launch_cvd.cc:184] 
>> assemble_cvd exited successfully.
>> launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:286] Started 
>> (pid: 2529630): /home/$USER/master/out/host/linux-x86/bin/run_cvd
>> launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:289] 
>> --undefok=report_anonymous_usage_stats
>> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:286] Started 
>> (pid: 2529637): /bin/bash
>> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] -c
>> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] egrep -h -e 
>> "^iff:.*" /proc/*/fdinfo/*
>> run_cvd E 03-30 15:12:18 2529630 2529630 users.cpp:48] Group virtaccess 
>> does not exist
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:367] The following files 
>> contain useful debugging information:
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:369]   Launcher log: 
>> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/launcher.log
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:371]   Android's logcat 
>> output: /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/logcat
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:372]   Kernel log: 
>> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/kernel.log
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:373]   Instance 
>> configuration: 
>> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/cuttlefish_config.json
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:374]   Instance 
>> environment: /tmp/acloud_cvd_temp/local-instance-1/.cuttlefish.sh
>> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:375] To access the 
>> console run: socat file:$(tty),raw,echo=0 
>> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/console
>>
>> I have attached cuttlefish.zip containing the "useful debugging 
>> information" files.
>>
>> Would you able to look into what is the issue?
>>
>> launcher.log mentions:
>>
>> [ERROR:src/main.rs:1281] The architecture failed to build the vm: error 
>> creating devices: failed to set up virtual socket device: failed to open 
>> vhost device: failed to open vhost device: Permission denied (os error 13)
>>
>> Thank you.
>>
>> On Friday, March 20, 2020 at 10:25:36 AM UTC+11, Kevin Cheng wrote:
>>
>>> hey Dean, wanted to check in to see if you were still having issues 
>>> after the fix was merged.
>>>
>>> On Thursday, March 12, 2020 at 12:50:35 PM UTC-7, Kevin Cheng wrote:

 Thanks for reporting that Dean, there's a pull request to fix it like 
 you recommended (https://github.com/google/android-cuttlefish/pull/45 
 
 ).

 On Wed, Mar 11, 2020 at 10:22 PM Dean Wheatley  wrote:

> Thanks Kevin.
>
> "acloud setup --host" failed, but provided reason:
>

[android-building] Re: Dex2oat failed to compile a boot image

[Michael Goffioul]

I found out I was missing this change:
https://android.googlesource.com/platform/libcore/+/271b4054b825efca3176c4ac11565e33cff5d09a
I cherry-picked it, but now I'm getting a different error:

dex2oatd F 03-30 19:11:33  6962  6962 unstarted_runtime.cc:2085] Calling
native method void android.system.OsConstants.initConstants() in an
unstarted non-transactional runtime


On Mon, Mar 30, 2020 at 6:59 PM Michael Goffioul 
wrote:

> On Mon, Mar 30, 2020 at 6:52 PM Michael Goffioul <
> michael.goffi...@gmail.com> wrote:
>
>> I'm still experimenting with android-r-preview-2, and very close to the
>> end of the build process, I'm getting the following error:
>>
>> FAILED:
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-apache-xml.vdex
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-bouncycastle.vdex
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-icu4j.vdex
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-core-libart.vdex
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot-okhttp.vdex
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.art
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.invocation
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.oat
>> out/soong/x86/dex_artjars/android/apex/com.android.art/javalib/x86/boot.vdex
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-apache-xml.oat
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-bouncycastle.oat
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-icu4j.oat
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-core-libart.oat
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot-okhttp.oat
>> out/soong/x86/dex_artjars_unstripped/android/apex/com.android.art/javalib/x86/boot.oat
>> dex2oatd F 03-30 18:38:12  5762  5762 class_linker.cc:8451] Check failed:
>> previous_size == size (previous_size=108, size=104) Ljava/lang/DexCache;
>> Runtime aborting...
>>
>> Any hint would be appreciated. I've never had that error in previous
>> Android versions, I'm not sure what to look for.
>>
>> Note that the above error is accompanied with a message to add
>> "--runtime-arg -verbose:verifier" to the
>>
>
> My apologies, I hit send too early. I just meant to say the additional
> flag didn't provide more information.
>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAB-99LvPSTaO7YEXLvorHOcKd%3DEi778-XPJyKC4E2YW2S7Hscw%40mail.gmail.com.

Re: [android-building] verbose: *kati*: slow included makefiles (1037.829698): art/Android.mk

['Dan Willemsen' via Android Building]

Interesting, 20 minutes still seems super excessive for that 

You'll probably save some amount of time sharing a single out directory
between devices, but not necessarily if you switch between them frequently,
as some of the device-specific files will clobber each other (this was
Soong trying to be smarter about sharing device-side code, until we came to
the point that we had too many configurations options to make that
reasonable ). And soong itself will re-run every time you switch devices
(kati may not, since we cache multiples of all of its outputs)

The one thing that would help you (at least until that github issue is
resolved) is to move the output directory outside of your source directory:
OUT_DIR=../out, etc. Then the find emulator wouldn't discover it.

Using a single output directory vs multiple output directories shouldn't
change the findemulator slowdown you're seeing as long as they're still in
the source directory. But the one thing a single output directory can slow
down is the initial ninja startup speed -- usually we expect to see that at
<=1s (depending on the machine), but that can grow if it needs to load
particularly large .ninja_log and .ninja_deps files, which will be shared
across all devices in a single output tree. It looks like yours is taking
~4s based on the trace. So your minimum incremental build times are
probably ~2x as long as they could be.

- Dan

On Mon, Mar 30, 2020 at 7:58 AM Yongqin Liu  wrote:

> Hi, Dan
>
> Thanks for the explanation!
>
> 在 2020年3月29日星期日 UTC+8上午3:15:52，Dan Willemsen写道：
>>
>> So that time was mostly spent initializing the find emulator:
>>
>> verbose: *kati*: init find emulator time: 1311.781312
>>
>> What that's doing is walking through your source tree and building up a
>> data structure to more efficiently (normally!) run `find` commands. This
>> can become very slow if you've added a symlink into your source tree
>> pointing to elsewhere on your filesystem (or a network filesystem). We've
>> also had reports that this can get very slow when you have a lot of output
>> trees under your source tree (being discussed in
>> https://github.com/google/kati/issues/184), but 20 minutes seems
>> excessive for that -- it claims that there are ~3M nodes in the cache:
>>
>
> Having a lot of output trees is my case.
> I build for following products under the same AOSP tree.
> beagle_x15/
> db845c/
> generic/
> generic_arm64/
> hikey/
> hikey960/
> vsoc_arm64
>
> I thought that would help to save time on the host tools/java files
> building...
>
>  verbose: *kati*: 3071468 find nodes
>
>>
>> One of my AOSP trees (after removing out/) is closer to 1M nodes (~2s),
>> and after a hikey960 build it has ~1.5M nodes (3.4s).
>>
> I checked log for another build which was done after out directory
> removed, the time is OK,
>
> Then what's your suggestion here:
> 1. use separate aosp tree for less product, like 2 or 3, my has 7 and cts,
> vts in the host out directory
> 2. I have not checked the details, and not verified it yet, do you think
> specifying the OUT out of the AOSP tree helps? still build multiply
> projects in the same out put directory.
> 3. I do not have data yet, just want to ask you here first, do you think
> build multiple products with the same output directory helps to save some
> time?
>  maybe my thought that it saves time on building the host binaries and
> java objects was wrong:(
>
>
> Thanks,
> Yongqin Liu
>
>
>
>
>> On Sat, Mar 28, 2020 at 8:36 AM Yongqin Liu  wrote:
>>
>>> Hi, All
>>>
>>> Anyone knows what's the problem with the step of "including
>>> out/soong/Android-hikey960.mk ..."
>>> and how to work around this problem?
>>>
>>> it took about 20 minutes to include during the build, which is almost
>>> half of the entire build time.
>>>
>>> The build was an incremental build after did repo sync.
>>>
>>> here is some information from the out/verbose.log.gz
>>>
>>> out/soong/make_vars-hikey960.mk was modified, regenerating...
>>> verbose: *kati*: regen check time: 0.079827
>>> verbose: *kati*: Stack size: 8376320 bytes
>>> [287/287] initializing build system ...
>>> verbose: *kati*: slow included makefiles (4.618866): build/make/core/
>>> base_rules.mk
>>> verbose: *kati*: slow included makefiles (4.618982): build/make/core/
>>> soong_cc_prebuilt.mk
>>> verbose: *kati*: slow included makefiles (4.604702): build/make/core/
>>> base_rules.mk
>>> verbose: *kati*: slow included makefiles (4.605250): build/make/core/
>>> soong_cc_prebuilt.mk
>>> verbose: *kati*: slow included makefiles (43.432355):
>>> out/soong/Android-hikey960.mk
>>> [288/491] including out/soong/Android-hikey960.mk ...
>>> verbose: *kati*: 3071468 find nodes
>>> verbose: *kati*: init find emulator time: 1311.781312
>>> verbose: *kati*: slow included makefiles (1311.898633): art/build/
>>> Android.cpplint.mk
>>> verbose: *kati*: slow included makefiles (1312.676836): art/Android.mk
>>> [289/491] including art/Android.mk ...
>>>
>>>
>>> 

Re: [android-building] Re: Error running local cuttlefish instance

['Kevin Cheng' via Android Building]

We've seen the permissions errors go away after a reboot, have you reboot
your host after running `acloud setup --host`?

On Mon, Mar 30, 2020 at 7:58 AM Dean Wheatley  wrote:

> Hi Kevin, the specific "acloud setup --host" is fixed.
>
> However, "acloud create --local-image --local-instance" is failing:
>
> $ acloud create --local-image --local-instance
> ...
>
> launch_cvd I 03-30 15:12:18 2529578 2529578 launch_cvd.cc:184]
> assemble_cvd exited successfully.
> launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:286] Started
> (pid: 2529630): /home/$USER/master/out/host/linux-x86/bin/run_cvd
> launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:289]
> --undefok=report_anonymous_usage_stats
> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:286] Started (pid:
> 2529637): /bin/bash
> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] -c
> run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] egrep -h -e
> "^iff:.*" /proc/*/fdinfo/*
> run_cvd E 03-30 15:12:18 2529630 2529630 users.cpp:48] Group virtaccess
> does not exist
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:367] The following files
> contain useful debugging information:
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:369]   Launcher log:
> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/launcher.log
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:371]   Android's logcat
> output: /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/logcat
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:372]   Kernel log:
> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/kernel.log
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:373]   Instance
> configuration:
> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/cuttlefish_config.json
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:374]   Instance
> environment: /tmp/acloud_cvd_temp/local-instance-1/.cuttlefish.sh
> run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:375] To access the
> console run: socat file:$(tty),raw,echo=0
> /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/console
>
> I have attached cuttlefish.zip containing the "useful debugging
> information" files.
>
> Would you able to look into what is the issue?
>
> launcher.log mentions:
>
> [ERROR:src/main.rs:1281] The architecture failed to build the vm: error
> creating devices: failed to set up virtual socket device: failed to open
> vhost device: failed to open vhost device: Permission denied (os error 13)
>
> Thank you.
>
> On Friday, March 20, 2020 at 10:25:36 AM UTC+11, Kevin Cheng wrote:
>
>> hey Dean, wanted to check in to see if you were still having issues after
>> the fix was merged.
>>
>> On Thursday, March 12, 2020 at 12:50:35 PM UTC-7, Kevin Cheng wrote:
>>>
>>> Thanks for reporting that Dean, there's a pull request to fix it like
>>> you recommended (https://github.com/google/android-cuttlefish/pull/45
>>> 
>>> ).
>>>
>>> On Wed, Mar 11, 2020 at 10:22 PM Dean Wheatley  wrote:
>>>
 Thanks Kevin.

 "acloud setup --host" failed, but provided reason:

 ...

 Start to install cuttlefish-common :
 git clone https://github.com/google/android-cuttlefish.git
 /tmp/tmpT5OIau/cf-common
 cd /tmp/tmpT5OIau/cf-common
 yes | sudo mk-build-deps -i -r -B
 dpkg-buildpackage -uc -us
 sudo apt-get install -y -f ../cuttlefish-common_*_amd64.deb
 Press 'y' to continue or anything else to do it myself and run acloud
 again[y/N]: y
 Run command: git clone https://github.com/google/android-cuttlefish.git
 /tmp/tmpT5OIau/cf-common
 cd /tmp/tmpT5OIau/cf-common
 yes | sudo mk-build-deps -i -r -B
 dpkg-buildpackage -uc -us
 sudo apt-get install -y -f ../cuttlefish-common_*_amd64.deb
 Cloning into '/tmp/tmpT5OIau/cf-common'...
 remote: Enumerating objects: 37, done.
 remote: Counting objects: 100% (37/37), done.
 remote: Compressing objects: 100% (29/29), done.
 remote: Total 2361 (delta 16), reused 19 (delta 8), pack-reused 2324
 Receiving objects: 100% (2361/2361), 623.77 KiB | 780.00 KiB/s, done.
 Resolving deltas: 100% (1338/1338), done.
 [sudo] password for dwhea:
 mk-build-deps: warning: debian/changelog(l13): badly formatted
 trailer line
 LINE:  -- Alistair Delva  Tue, 03 Mar 2020 03:18:25
 -0800
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
 yes: standard output: Broken pipe
 dpkg-buildpackage: warning: debian/changelog(l13): badly formatted
 trailer line
 LINE:  -- Alistair Delva  Tue, 03 Mar 2020 03:18:25
 -0800
  dpkg-source --before-build .
 dpkg-source: warning: cf-common/debian/changelog(l13): badly formatted
 trailer line
 LINE:  -- Alistair Delva  Tue, 03 Mar 2020 03:18:25
 

Re: [android-building] Disallowed PATH tool "m4", but used by flex

['Dan Willemsen' via Android Building]

As a reminder:

This preview is not a full platform update and only for reference.


It is not expected that everything will build, as it only contains updates
to some projects.

For this breakage in particular, you'll need a change like this one, which
fixes up a bunch of things around how mesa was using flex/bison:
https://android-review.googlesource.com/c/platform/external/mesa3d/+/1203548

- Dan

On Mon, Mar 30, 2020 at 7:58 AM Michael Goffioul 
wrote:

> I'm experimenting with android-r-preview-2 and found a problem compiling
> mesa, which didn't occur with android-10. The error occurs when running
> flex:
>
> 23:56:24 Disallowed PATH tool "m4" used: []string{"m4", "-P"}
> 23:56:24 See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
> [  0% 1/74788] Mesa Lex: libmesa_glsl <=
> external/mesa/src/compiler/glsl/glcpp/glcpp-lex.l
> FAILED:
> out/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
> /bin/bash -c "prebuilts/build-tools/linux-x86/bin/flex --nounistd
> -oout/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
> external
> /mesa/src/compiler/glsl/glcpp/glcpp-lex.l"
> "m4" is not allowed to be used. See
> https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
> for more information.
>
> From what I understand, flex internally calls "m4" (according to this
> reference:
> https://www.cs.virginia.edu/~cr4bd/flex-manual/M4-Dependency.html).
>
> Any pointer in the right direction would be appreciated, thanks.
>
> Michael.
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/CAB-99LtxMUAWGZG2SbnjKB0iOiNAQV5R5oZP%2BHaUaeeW%3D1LZMA%40mail.gmail.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CALQgHd%3DKLk8dSES94QAgJqgre99PrGJKBiBLwHSOOAcwudSeZg%40mail.gmail.com.

Re: [android-building] Generate external/llvm Intrinsics.gen and Attributes.inc on android10

[Paschalis Mpeis]

I've eventually made this work. My last issue was due to the target 
*libLLVM_android* being only available for host architectures (linux/darwin 
x86).
I made another target just for Android, and it did work, but since llvm 
version was too old (3.8 in particular), including those c++11 headers in 
art/compiler
have caused a lot of other issues. Making it another library and using that 
one from art/compiler would still wouldn't solve it.

Tinkering some art headers was messy, so I decided that the only solution 
was to use a more up-to-date llvm sources.
For this I've tried many many things, including:
1. cross compiling llvm, which worked but linking *libLLVM.*so against 
*libart-compiler.so* wouldn't, because Android NDK, has modified the std 
namespace. So I had unresolved symbols.
2. tried to compile NDK from sources to "work around" the namespace issue 
but I eventually gave up
3. tried to compile using the exact same flags that AOSP users for libart 
(except the c++11 one which LLVM requires), but stuck on issues as well.

I ended up doing what I've tried to avoid: *integrated llvm9 sources into 
the soong build system as another external project*, in a similar fashion 
with the outdated external/llvm.
To avoid collisions I named it external/llvmx (also for any blueprint 
targets as well), since the outdated llvm has dependencies with other parts 
of the AOSP.
I've created new blueprint targets (and referenced them in existing ones) 
for new code that were required for: libLLVM.so, llc, opt, and llvm-link.

The only difference from the external/llvm build process is that I didn't 
followed the same route for files generated by llvm's tblgen.
The tblgen dependencies have increased, and each of them required special 
handling (targets in .bp backed by some go lang scripts).
So I removed all the tblgen related targets from .bp files, and I'm 
including them as prebuilt headers from my cross-compiled version.

I can now link libLLVM.so against libart-compiler.so and actually use it. 
llvm9 headers do not cause any issues now.

Cheers,
Paschalis





On Tuesday, March 17, 2020 at 7:42:16 PM UTC+2, Paschalis Mpeis wrote:
>
> Hi again,
>
> I hope everybody is doing well given these days' circumstances!
>
> I have a follow-up question on my previous attempts to use LLVM.
> What I want is to include *libLLVM_android* on l*ibart-compiler* and use 
> it on an arm64 device (sailfish) in particular.
>
> Now, I can successfully compile llvm components I need using:
> m libLLVM_android opt llc llvm-linker
>
> Then I install the library and the 3 tools on a sailfish device, and when 
> executing llc for example I can see that it can successfully utilize the 
> *libLLVM_android* library.
> But when I try to include the libLLVM_android on art/compiler/Android.bp I 
> get issues.
>
> Here's my changes:
> *art/compiler/Android.bp:*
> libart_cc_defaults {
> name: "some_llvm_defaults",
> defaults: [
> // I am not using llvm-defaults as compilation will break on 
> warnings like: -Wc++14-extensions
> // "llvm-defaults",
> "force_build_llvm_components",
> ],
> target: {
> android: {
> srcs: [
> // my additional .cc files go here..
> ],
> },
> },
> // I think this is the proper way to include the headers
> header_libs: ["llvm-headers"],
> // not sure about the next 2 lines
> // export_shared_lib_headers: ["libLLVM_android"],
> // compile_multilib: "first",
>
> // that's how I should include the library I think, but it gives me 
> the error#1 listed below
> shared_libs: ["libLLVM_android"],
> cflags: [
> // some flags necessary for LLVM
> "-D__STDC_LIMIT_MACROS",
> "-D__STDC_CONSTANT_MACROS",
> "-Wno-unused-parameter",
> ],
> // headers shouldn't be included like this I think, but instead
> // with someting like header_libs that I did above
> include_dirs: [
> "external/llvm/include",
> ],
> }
>
> On the external/llvm/Android.bp I can see here 
> 
>  that 
> it does export the relevant header directories for android targets,
> and since I have successfully compiled and installed libLLVM_android on a 
> device, I can't see why it won't work.
>
> The error#1 is:
>
>> out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list 
> -b out/soong
> -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-
> globs.ninja -o
> out/soong/build.ninja Android.bp
>
> internal error: panic in WalkDeps(module "apex_test_build_features" 
> variant "android_common_apex_test_build_features",
>
> github.com/google/blueprint.(*baseModuleContext).WalkDeps.func1, ) for 
> dependency module "prebuilt_libLLVM_android"
> variant "android_arm_armv8-a_kryo_core_shared_apex_test_build_features" in 
> GenerateBuildActions for 

Re: [android-building] Re: Error running local cuttlefish instance

[Dean Wheatley]

Hi Kevin, the specific "acloud setup --host" is fixed.

However, "acloud create --local-image --local-instance" is failing:

$ acloud create --local-image --local-instance
...

launch_cvd I 03-30 15:12:18 2529578 2529578 launch_cvd.cc:184] assemble_cvd 
exited successfully.
launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:286] Started 
(pid: 2529630): /home/$USER/master/out/host/linux-x86/bin/run_cvd
launch_cvd I 03-30 15:12:18 2529578 2529578 subprocess.cpp:289] 
--undefok=report_anonymous_usage_stats
run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:286] Started (pid: 
2529637): /bin/bash
run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] -c
run_cvd I 03-30 15:12:18 2529630 2529630 subprocess.cpp:289] egrep -h -e 
"^iff:.*" /proc/*/fdinfo/*
run_cvd E 03-30 15:12:18 2529630 2529630 users.cpp:48] Group virtaccess 
does not exist
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:367] The following files 
contain useful debugging information:
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:369]   Launcher log: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/launcher.log
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:371]   Android's logcat 
output: /tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/logcat
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:372]   Kernel log: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/kernel.log
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:373]   Instance 
configuration: 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/cuttlefish_config.json
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:374]   Instance 
environment: /tmp/acloud_cvd_temp/local-instance-1/.cuttlefish.sh
run_cvd I 03-30 15:12:18 2529630 2529630 main.cc:375] To access the console 
run: socat file:$(tty),raw,echo=0 
/tmp/acloud_cvd_temp/local-instance-1/cuttlefish_runtime.1/console

I have attached cuttlefish.zip containing the "useful debugging 
information" files.

Would you able to look into what is the issue?

launcher.log mentions:

[ERROR:src/main.rs:1281] The architecture failed to build the vm: error 
creating devices: failed to set up virtual socket device: failed to open 
vhost device: failed to open vhost device: Permission denied (os error 13)

Thank you.

On Friday, March 20, 2020 at 10:25:36 AM UTC+11, Kevin Cheng wrote:

> hey Dean, wanted to check in to see if you were still having issues after 
> the fix was merged.
>
> On Thursday, March 12, 2020 at 12:50:35 PM UTC-7, Kevin Cheng wrote:
>>
>> Thanks for reporting that Dean, there's a pull request to fix it like you 
>> recommended (https://github.com/google/android-cuttlefish/pull/45 
>> 
>> ).
>>
>> On Wed, Mar 11, 2020 at 10:22 PM Dean Wheatley > > wrote:
>>
>>> Thanks Kevin.
>>>
>>> "acloud setup --host" failed, but provided reason:
>>>
>>> ...
>>>
>>> Start to install cuttlefish-common :
>>> git clone https://github.com/google/android-cuttlefish.git 
>>> /tmp/tmpT5OIau/cf-common
>>> cd /tmp/tmpT5OIau/cf-common
>>> yes | sudo mk-build-deps -i -r -B
>>> dpkg-buildpackage -uc -us
>>> sudo apt-get install -y -f ../cuttlefish-common_*_amd64.deb
>>> Press 'y' to continue or anything else to do it myself and run acloud 
>>> again[y/N]: y
>>> Run command: git clone https://github.com/google/android-cuttlefish.git 
>>> /tmp/tmpT5OIau/cf-common
>>> cd /tmp/tmpT5OIau/cf-common
>>> yes | sudo mk-build-deps -i -r -B
>>> dpkg-buildpackage -uc -us
>>> sudo apt-get install -y -f ../cuttlefish-common_*_amd64.deb
>>> Cloning into '/tmp/tmpT5OIau/cf-common'...
>>> remote: Enumerating objects: 37, done.
>>> remote: Counting objects: 100% (37/37), done.
>>> remote: Compressing objects: 100% (29/29), done.
>>> remote: Total 2361 (delta 16), reused 19 (delta 8), pack-reused 2324
>>> Receiving objects: 100% (2361/2361), 623.77 KiB | 780.00 KiB/s, done.
>>> Resolving deltas: 100% (1338/1338), done.
>>> [sudo] password for dwhea: 
>>> mk-build-deps: warning: debian/changelog(l13): badly formatted 
>>> trailer line
>>> LINE:  -- Alistair Delva > Tue, 03 Mar 
>>> 2020 03:18:25 -0800
>>> Starting pkgProblemResolver with broken count: 0
>>> Starting 2 pkgProblemResolver with broken count: 0
>>> Done
>>> yes: standard output: Broken pipe
>>> dpkg-buildpackage: warning: debian/changelog(l13): badly formatted 
>>> trailer line
>>> LINE:  -- Alistair Delva > Tue, 03 Mar 
>>> 2020 03:18:25 -0800
>>>  dpkg-source --before-build .
>>> dpkg-source: warning: cf-common/debian/changelog(l13): badly formatted 
>>> trailer line
>>> LINE:  -- Alistair Delva > Tue, 03 Mar 
>>> 2020 03:18:25 -0800
>>>  fakeroot debian/rules clean
>>>  dpkg-source -b .
>>> dpkg-source: warning: cf-common/debian/changelog(l13): badly formatted 
>>> trailer line
>>> LINE:  -- Alistair Delva > Tue, 03 Mar 
>>> 2020 03:18:25 -0800
>>>  debian/rules build
>>>  fakeroot debian/rules binary
>>> 

[android-building] Re: Pixel 4XL (coral) - No call sound

[Sharon]

I found a suspicious line in the logcat:
hardware_info: hw_info_append_hw_type : device_name = vi-feedback

Is it an 'audio loopback'?

On Saturday, 28 March 2020 01:22:09 UTC+3, Sharon wrote:
>
> Hi All
>
> I built AOSP 10 from source according to Google documentation, including 
> the binaries that match the version of AOSP
> no cherry picks, no code changes only Vanilla AOSP - but no in-call audio 
>
> What I did:
> repo init -u https://android.googlesource.com/platform/manifest -b 
> android-10.0.0_r31
> pull and extract google drivers and qcom from here - 
> https://developers.google.com/android/drivers#coralqq2a.200305.003
>
> Anyone knows the fix or can point me to files that could fix it
> thanks!
>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/ab5757cd-77bb-45ee-97b4-95622c9d7dd7%40googlegroups.com.

[android-building] Disallowed PATH tool "m4", but used by flex

[Michael Goffioul]

I'm experimenting with android-r-preview-2 and found a problem compiling
mesa, which didn't occur with android-10. The error occurs when running
flex:

23:56:24 Disallowed PATH tool "m4" used: []string{"m4", "-P"}
23:56:24 See
https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
for more information.
[  0% 1/74788] Mesa Lex: libmesa_glsl <=
external/mesa/src/compiler/glsl/glcpp/glcpp-lex.l
FAILED:
out/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
/bin/bash -c "prebuilts/build-tools/linux-x86/bin/flex --nounistd
-oout/target/product/x86/gen/STATIC_LIBRARIES/libmesa_glsl_intermediates/glsl/glcpp/glcpp-lex.c
external
/mesa/src/compiler/glsl/glcpp/glcpp-lex.l"
"m4" is not allowed to be used. See
https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools
for more information.

>From what I understand, flex internally calls "m4" (according to this
reference: https://www.cs.virginia.edu/~cr4bd/flex-manual/M4-Dependency.html
).

Any pointer in the right direction would be appreciated, thanks.

Michael.

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CAB-99LtxMUAWGZG2SbnjKB0iOiNAQV5R5oZP%2BHaUaeeW%3D1LZMA%40mail.gmail.com.

Re: [android-building] verbose: *kati*: slow included makefiles (1037.829698): art/Android.mk

[Yongqin Liu]

Hi, Dan

Thanks for the explanation!

在 2020年3月29日星期日 UTC+8上午3:15:52，Dan Willemsen写道：
>
> So that time was mostly spent initializing the find emulator:
>
> verbose: *kati*: init find emulator time: 1311.781312
>
> What that's doing is walking through your source tree and building up a 
> data structure to more efficiently (normally!) run `find` commands. This 
> can become very slow if you've added a symlink into your source tree 
> pointing to elsewhere on your filesystem (or a network filesystem). We've 
> also had reports that this can get very slow when you have a lot of output 
> trees under your source tree (being discussed in 
> https://github.com/google/kati/issues/184), but 20 minutes seems 
> excessive for that -- it claims that there are ~3M nodes in the cache:
>

Having a lot of output trees is my case.
I build for following products under the same AOSP tree.
beagle_x15/
db845c/
generic/
generic_arm64/ 
hikey/
hikey960/
vsoc_arm64

I thought that would help to save time on the host tools/java files 
building...

 verbose: *kati*: 3071468 find nodes

>
> One of my AOSP trees (after removing out/) is closer to 1M nodes (~2s), 
> and after a hikey960 build it has ~1.5M nodes (3.4s).
>
I checked log for another build which was done after out directory  
removed, the time is OK, 

Then what's your suggestion here:
1. use separate aosp tree for less product, like 2 or 3, my has 7 and cts, 
vts in the host out directory
2. I have not checked the details, and not verified it yet, do you think 
specifying the OUT out of the AOSP tree helps? still build multiply 
projects in the same out put directory.
3. I do not have data yet, just want to ask you here first, do you think 
build multiple products with the same output directory helps to save some 
time?
 maybe my thought that it saves time on building the host binaries and 
java objects was wrong:(


Thanks,
Yongqin Liu


 

> On Sat, Mar 28, 2020 at 8:36 AM Yongqin Liu  > wrote:
>
>> Hi, All
>>
>> Anyone knows what's the problem with the step of "including 
>> out/soong/Android-hikey960.mk ..."
>> and how to work around this problem?
>>
>> it took about 20 minutes to include during the build, which is almost 
>> half of the entire build time.
>>
>> The build was an incremental build after did repo sync. 
>>
>> here is some information from the out/verbose.log.gz
>>
>> out/soong/make_vars-hikey960.mk was modified, regenerating...
>> verbose: *kati*: regen check time: 0.079827
>> verbose: *kati*: Stack size: 8376320 bytes
>> [287/287] initializing build system ...
>> verbose: *kati*: slow included makefiles (4.618866): build/make/core/
>> base_rules.mk
>> verbose: *kati*: slow included makefiles (4.618982): build/make/core/
>> soong_cc_prebuilt.mk
>> verbose: *kati*: slow included makefiles (4.604702): build/make/core/
>> base_rules.mk
>> verbose: *kati*: slow included makefiles (4.605250): build/make/core/
>> soong_cc_prebuilt.mk
>> verbose: *kati*: slow included makefiles (43.432355): 
>> out/soong/Android-hikey960.mk
>> [288/491] including out/soong/Android-hikey960.mk ...
>> verbose: *kati*: 3071468 find nodes
>> verbose: *kati*: init find emulator time: 1311.781312
>> verbose: *kati*: slow included makefiles (1311.898633): art/build/
>> Android.cpplint.mk
>> verbose: *kati*: slow included makefiles (1312.676836): art/Android.mk
>> [289/491] including art/Android.mk ...
>>
>>
>> For details, please check the attached build log.
>>
>>
>> Thanks in advance!
>>
>>
>> Best Regards,
>> Yongqin Liu
>>
>> -- 
>> -- 
>> You received this message because you are subscribed to the "Android 
>> Building" mailing list.
>> To post to this group, send email to android-...@googlegroups.com 
>> 
>> To unsubscribe from this group, send email to
>> android-...@googlegroups.com 
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to android-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/android-building/eebd86b2-83c0-460e-a26d-6cd5af31fb20%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it,