[android-building] Re: Choosing a target device

['Glenn Kasten' via Android Building]

Please see https://source.android.com/setup/build/building#choose-a-target
and https://source.android.com/setup/build/running#selecting-device-build

On Thursday, October 8, 2020 at 10:34:11 AM UTC-7, Mahnoor Malik wrote:
>
> Dear all.
>
>
> I am building android for the first time. I donot have to flash the os on 
> a hardware device and have to work on emulator only ( university project ). 
> I have downloaded the master branch of android repo. Let me know which 
> target should I select for lunch command. Here many devices are listed for 
> android 11. I need suggestions
>
> https://source.android.com/setup/start/build-numbers
>
> Regards,
> Mahnoor
>

-- 
-- 
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/2df31138-e944-4664-91e3-709765a0e31fo%40googlegroups.com.

[android-building] Re: Android 11 Released

['Glenn Kasten' via Android Building]

Miguel, thank you for mentioning these problems. Would you mind please 
filing bug report(s) here 

and / or uploading CLs 
 that fix, 
since it sounds like you do have fixes?
The reason is that is difficult to track bugs and CLs here in the 
discussion group,
and so we generally prefer them in the bug tracking system and Gerrit for 
CLs.
Thanks so much!
Glenn

On Thursday, September 17, 2020 at 2:10:52 PM UTC-7, Miguel Martinez wrote:
>
> Few bugs in the android-msm-sunfish-4.14-android11 branch 
>
> The last merge in this repo:
> kernel/msm/data-kernel
> for branch: 
> android-msm-sunfish-4.14-android11
>
> Contains a mismerge in the last merge, commit 
> d88d11796e03f56df05d25333e11767b094b2cae
> Line 2640 of drivers/rmnet/shs/rmnet_shs_wq.c
> +<<< HEAD +=== 
> + jiffies = msecs_to_jiffies(rmnet_shs_wq_interval_ms); 
> + 
> +>>> LA.UM.9.1.R1.10.00.00.604.038  
>
> The kernel/msm-modules/fts_touch repo
> this version of the driver is older than the R-Beta3 branch we had in the 
> beta release.
> Touch does not work with this android11 branch version of the driver. If I 
> revert this repo to the rbeta3 branch version, then touch works fine again.
>
> Final issue is the qcacld driver needs hardcoded to init by default or it 
> does not function, will not turn on. But that's not a big deal and an easy 
> fix.
> On Tuesday, September 8, 2020 at 6:23:49 PM UTC-5 Bill Yi wrote:
>
>>
>> We pushed reference Android Mainline source with the following tags:
>> - android-mainline-11.0.0_r1
>>
>> bill
>>
>>
>> On Tuesday, September 8, 2020 at 5:59:50 PM UTC-4 Bill Yi wrote:
>>
>>> Hi all,
>>>
>>> Android 11 source code is now available. The following builds, tags, and 
>>> devices are supported:
>>>  - RP1A.200720.009, android-11.0.0_r1, Pixel 2, Pixel 2 XL, Pixel 3, 
>>> Pixel 3 XL, Pixel 4, Pixel 4 XL, Pixel 3a XL, Pixel 3
>>>  - RP1A.200720.010, android-11.0.0_r2, Pixel 4a
>>>  - RP1A.200720.011, android-11.0.0_r3, Pixel 4a
>>>
>>> The corresponding factory images, ota images, and proprietary binaries 
>>> are available at
>>>  https://developers.google.com/android/images
>>>  https://developers.google.com/android/ota
>>>  https://developers.google.com/android/drivers
>>>
>>> We pushed a reference "android11-dev" branch.
>>>
>>> We have pushed the corresponding kernel projects for the following 
>>> devices:
>>>
>>> Tag  | Project| Branch  
>>> | Device
>>> android-11.0.0_r0.1 | kernel/msm  | 
>>> android-msm-wahoo-4.4-android11 | Pixel 2 XL, Pixel 2
>>> android-11.0.0_r0.1 | kernel/arm64| 
>>> android-amber-intel-linux-4.7-android11 | Pixel 2 XL, Pixel 2
>>> android-11.0.0_r0.2 | kernel/msm  | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-extra| 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/qcacld   | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.2 | kernel/msm-modules/wlan-fw-api  | 
>>> android-msm-crosshatch-4.9-android11| Pixel 3 XL, Pixel 3
>>> android-11.0.0_r0.3 | kernel/msm  | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-extra| 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/qcacld   | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.3 | kernel/msm-modules/wlan-fw-api  | 
>>> android-msm-bonito-4.9-android11| Pixel 3a XL, Pixel 3a
>>> android-11.0.0_r0.4 | kernel/msm  | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-extra| 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/data-kernel  | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/fts_touch| 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/qca-wfi-host-cmn | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | kernel/msm-modules/qcacld   | 
>>> android-msm-coral-4.14-android11| Pixel 4 XL, Pixel 4
>>> android-11.0.0_r0.4 | 

Re: [android-building] AOSP Resources

['Glenn Kasten' via Android Building]

The classic book 
is 
https://www.amazon.com/Embedded-Android-Porting-Extending-Customizing/dp/1449308295
but it's old and may only be available used.

On Tuesday, September 15, 2020 at 8:16:21 AM UTC-7, Igor Kukushkin wrote:
>
> Duh try narrowing the question down, way too much possibilities there.
>
> Try building the basic targets first (Cuttlefish, emulator image, generic 
> GSI, some Pixel/Nexus targets, Auto if curious). Then start looking into 
> how makefiles (.mk)/Bazel is working. Then try the same thing with any 
> custom fork, and proceed to experimenting (adding some HAL changes, custom 
> system server services), or look into hooking (frida/xposed/magisk) - that 
> alone is a great experience.
> Do try to understand the reasoning behind using Gerrit, that's kinda 
> important - then find a couple projects (forks) using it and see what 
> changes are common these days.
>
> On Mon, Sep 14, 2020 at 6:37 PM Heman Parbhakar  
> wrote:
>
>> Hello Everyone,
>>
>> Can anyone tell me good resources to learn Android ROM Development from 
>> scratch. Thanks in Advance!
>>
>>
>> -- 
>> -- 
>> 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/6e3aa5df-2457-48e9-81d0-0a7e1fd1fcdbn%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, 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/89371d54-709a-4aef-ae4b-89186b47f563o%40googlegroups.com.

[android-building] Re: AOSP Resources

['Glenn Kasten' via Android Building]

I'm not quite sure what you mean by "from scratch", but I recommend 
starting here:
https://source.android.com/
in particular tab "set up" and then the sub-tabs of "set up".

In general it is usually easier to first build for an AOSP-supported target 
device
before attempting to port to another device. Supported devices are listed 
here:
https://source.android.com/setup/build/running#selecting-device-build

On Monday, September 14, 2020 at 9:37:46 AM UTC-7, Heman Parbhakar wrote:
>
> Hello Everyone,
>
> Can anyone tell me good resources to learn Android ROM Development from 
> scratch. Thanks in Advance!
>
>
>

-- 
-- 
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/33cbcb6d-6d81-4af5-9343-6b9b0c3486cdo%40googlegroups.com.

[android-building] Re: Building Android Automotive for Raspberry Pi [closed]

['Glenn Kasten' via Android Building]

See list of supported build targets here:
https://source.android.com/setup/build/running#selecting-device-build

On Thursday, September 10, 2020 at 8:13:50 AM UTC-7, Salvatore Amodio wrote:
>
> I would like to know how building Android Automotive OS for Raspberry Pi? 
> I downloaded the source through Repo Launcher from
>
> https://source.android.com/setup/build/downloading
>
> Then I initialized the environment:
>
> -- source build/envsetup.sh -- build/envsetup.sh
>
> I chose the target:
>
> -- lunch aosp_car_arm64-userdebug
>
> and I launched the last command:
>
> -- time make -j$(nproc)
>
> The image has been created is only for the emulator or it can be flashed 
> on the Rpi 4?
>

-- 
-- 
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/239b7efe-73ed-4b8f-9d6b-d86d3426884eo%40googlegroups.com.

[android-building] Re: Run emulator on Android 11 (R)

['Glenn Kasten' via Android Building]

Preview source code is incomplete and for reference only, and is not 
intended to be buildable or fully executable.

On Friday, August 28, 2020 at 11:49:48 AM UTC-7, Nguyễn Trung Thành wrote:
>
> Dear all,
>
> I am trying to get source code from master from to build. With few 
> adjustment I can build this source code. However, emulator isn't started as 
> well. I check logcat and there are some errors. 
>
> Here is error:
> 08-27 08:04:46.366   718   718 D SystemServerTiming: 
> MakePackageManagerServiceReady took to complete: 205ms
> 08-27 08:04:46.366   718   718 E Zygote  : System zygote died with 
> exception
> 08-27 08:04:46.366   718   718 E Zygote  : 
> java.lang.IllegalStateException: Signature|privileged permissions not in 
> privapp-permissions whitelist: {com.android.car.developeroptions: 
> android.permission.READ_PRIVILEGED_PHONE_STATE}
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2983)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3044)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21192)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.startOtherServices(SystemServer.java:2035)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.run(SystemServer.java:536)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.server.SystemServer.main(SystemServer.java:362)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> java.lang.reflect.Method.invoke(Native Method)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
> 08-27 08:04:46.366   718   718 E Zygote  : at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:906)
> 08-27 08:04:46.366   718   718 D AndroidRuntime: Shutting down VM
> 08-27 08:04:46.366   718   718 E AndroidRuntime: *** FATAL EXCEPTION IN 
> SYSTEM PROCESS: main
> 08-27 08:04:46.366   718   718 E AndroidRuntime: 
> java.lang.IllegalStateException: Signature|privileged permissions not in 
> privapp-permissions whitelist: {com.android.car.developeroptions: 
> android.permission.READ_PRIVILEGED_PHONE_STATE}
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2983)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:122)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:3044)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21192)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.startOtherServices(SystemServer.java:2035)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.run(SystemServer.java:536)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.server.SystemServer.main(SystemServer.java:362)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> java.lang.reflect.Method.invoke(Native Method)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
> 08-27 08:04:46.366   718   718 E AndroidRuntime: at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:906)
> 08-27 08:04:46.367   718   718 I DropBoxManagerService: add 
> tag=system_server_crash isTagEnabled=true flags=0x2
>
> I see something relate to READ_PRIVILEGED_PHONE_STATE  but I don't know 
> how to fix it.
> Could you help me to check the problem?
>
> Best regards,
> Thanh
>

-- 
-- 
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 

[android-building] Re: Help! Disk space getting nearly full because of Android's source files

['Glenn Kasten' via Android Building]

I'm not sure what's causing the tmp_pack_ problem.
But you might need to start over with a completely new download, and on a 
machine with a lot more disk space available.
That is:
 - make a backup of any of your important files
 - delete your current download area, including hidden directories and 
hidden files within the download area
 - check your disk space and make sure you have *lots* available, and 
consider adding even more space
 - start a new download

On Wednesday, August 26, 2020 at 6:30:01 AM UTC-7, `mCT wrote:
>
> @Glenn Kasten
>
> Hi,
> I see that one of my two messages, which I posted yesterday, hasn't 
> appeared here yet, while the other has appeared. I am talking about the 
> message, which I posted in response to your reply of 22 Aug to me, in which 
> you are asking me to see an article based on disk space requirements.
> So, I would ask you to kindly check my that message also, as it is quite 
> important in this conversation. It would be very kind of you to share the 
> update regarding that message.
>
> thanks,
> Waiting for your help `n reply.
>
> On Sunday, August 23, 2020 at 8:44:07 PM UTC+5:30 `mCT wrote:
>
>> @ Glenn Kasten
>>
>> In addition to my earlier message, I forgot to say that, I have also 
>> written my problem in one message outside of this conversation. It is 
>> here. 
>> 
>>
>> On Saturday, August 22, 2020 at 11:47:11 PM UTC+5:30 Glenn Kasten wrote:
>>
>>> Please see this article on disk requirements:
>>> https://source.android.com/setup/build/requirements
>>>
>>> Are you finding that it actually needs more free disk space than the 
>>> amount listed?
>>> If so please reply and we'll update the documentation to the correct 
>>> amount.
>>>
>>> On the other hand, if the amount listed is correct and your machine just 
>>> doesn't have that much free space,
>>> really the only solution is to create more free space, for example by 
>>> adding another larger drive.
>>>
>>> On Saturday, August 22, 2020 at 11:11:26 AM UTC-7, `mCT wrote:


 Hi everyone,
 I would just like to ask for help. While downloading Android's source, 
 my disk's space is getting nearly full because of these 'tmp_pack_...' 
 files which are of many GBs, and I am not able to find a solution.
 It would be very kind of anyone who can guide me what to do of these 
 'tmp_pack_...' files, as deleting them will not solve my problem 
 completely, as when I have to download Android's source again, these files 
 will start getting accumulated again, but as I have to pause downloading 
 the source because of Internet data getting finished, so I also wanted to 
 know if it's possible to pause downloading the source, then how to do it?
>>>
>>>

-- 
-- 
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/60c13dcf-6813-445f-8089-58a9f9becca7o%40googlegroups.com.

[android-building] Re: Help! Disk space getting nearly full because of Android's source files

['Glenn Kasten' via Android Building]

Please see this article on disk requirements:
https://source.android.com/setup/build/requirements

Are you finding that it actually needs more free disk space than the amount 
listed?
If so please reply and we'll update the documentation to the correct amount.

On the other hand, if the amount listed is correct and your machine just 
doesn't have that much free space,
really the only solution is to create more free space, for example by 
adding another larger drive.

On Saturday, August 22, 2020 at 11:11:26 AM UTC-7, `mCT wrote:
>
>
> Hi everyone,
> I would just like to ask for help. While downloading Android's source, my 
> disk's space is getting nearly full because of these 'tmp_pack_...' files 
> which are of many GBs, and I am not able to find a solution.
> It would be very kind of anyone who can guide me what to do of these 
> 'tmp_pack_...' files, as deleting them will not solve my problem 
> completely, as when I have to download Android's source again, these files 
> will start getting accumulated again, but as I have to pause downloading 
> the source because of Internet data getting finished, so I also wanted to 
> know if it's possible to pause downloading the source, then how to do it?

-- 
-- 
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/c30771f6-b277-4f98-8c1c-92aa7e325305o%40googlegroups.com.

[android-building] Re: Build android-r-preview-4 on macOS 10.15 failed. Did anyone succeed?

['Glenn Kasten' via Android Building]

Preview source code is incomplete and for reference only, and is not 
intended to be buildable.

On Wednesday, August 5, 2020 at 7:22:56 PM UTC-7, Lee Prime wrote:
>
> After the repo sync was done , I start do the following steps. 
>
> source build/envsetup.sh  # this works fine. 
>
> lunch # there was several problems. Here they are.
>
> ===
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> dyld: Library not loaded: @rpath/libcrypto-host.dylib
>   Referenced from: 
> /Volumes/AOSP/android-r-preview-4/prebuilts/build-tools/path/darwin-x86/date
>   Reason: image not found
> /bin/bash: line 1: 68924 Doneecho a
>  68925 Abort trap: 6   | sed -E -e 's/a/b/' 2> /dev/null
> /bin/bash: line 1: 68927 Doneecho c
>  68928 Abort trap: 6   | sed -r -e 's/c/d/' 2> /dev/null
> ==
>
> I fiexed the dyld problem by using install_name_tool. 
> But there still 2 problem to be solved. 
>
> =
> /bin/bash: line 1: 68924 Doneecho a
>  68925 Abort trap: 6   | sed -E -e 's/a/b/' 2> /dev/null
> /bin/bash: line 1: 68927 Doneecho c
>  68928 Abort trap: 6   | sed -r -e 's/c/d/' 2> /dev/null
> -===
>
> How should I fix it?
>
>

-- 
-- 
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/66bd3038-b53c-47ff-9c29-80453501cd41o%40googlegroups.com.

[android-building] Re: increase the memory used for building

['Glenn Kasten' via Android Building]

> Does the the build system take the full advantage of the available memory 
in the building machine?
Yes, by default.

> Lets say I have 64Gb RAM does it use all the memory?
Yes, if that much is needed, except for memory used by the host OS/kernel 
and other processes running on same machine.

> If there is a limit how I can change it? is there an option to increase 
it?
There is no overall limit or option for the build, but specific build tools 
may have limits and options.
Generally it is not necessary to configure these.

The host OS may have facilities for limits ...
for example Linux has cgroups, and bash has the ulimit command.
But you will usually not need to use these.


On Tuesday, July 21, 2020 at 7:32:36 AM UTC-7, Kbc K wrote:
>
> Hi all,
>
> I have a question about AOSP build system memory usage.
>
> Does the the build system take the full advantage of the available memory 
> in the building machine? 
> Lets say I have 64Gb RAM does it use all the memory?
>
> If there is a limit how I can change it? is there an option to increase 
> it? 
>
> BR
> K
>

-- 
-- 
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/0b28bbee-0858-469c-8430-029cd55a28bao%40googlegroups.com.

[android-building] Re: acloud fails on Ubuntu 20.04

['Glenn Kasten' via Android Building]

Please file a bug here:

https://source.android.com/setup/contribute/report-bugs

On Thursday, June 18, 2020 at 7:32:05 AM UTC-7, Ismael Vidal wrote:
>
> I have the same problem on Ubuntu 20.04. :(
>
> On Tuesday, June 2, 2020 at 12:35:10 PM UTC-4, Dean Wheatley wrote:
>>
>> Irrespective of running python version (2.7.18rc1 or 3.8.2) on Ubuntu 
>> 20.04, acloud fails as below:
>>
>> $ acloud setup --host
>>
>> Welcome to
>> 
>>___  ___     __  _ 
>>   / _ |/ ___/ /  / __ \/ / / / _ \ 
>>  / __ / /__/ /__/ /_/ / /_/ / // /  
>> /_/ |_\___//\/\// 
>>   
>>
>> Traceback (most recent call last):
>>   File "/tmp/Soong.python_ym5s7lig/acloud/public/acloud_main.py", line 
>> 440, in 
>> EXIT_CODE, EXCEPTION_STACKTRACE = main(sys.argv[1:])
>>   File "/tmp/Soong.python_ym5s7lig/acloud/public/acloud_main.py", line 
>> 419, in main
>> setup.Run(args)
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/setup.py", line 73, in Run
>> subtask.Run(force_setup=args.force)
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/base_task_runner.py", 
>> line 97, in Run
>> if self.ShouldRun() or force_setup:
>>   File "/tmp/Soong.python_ym5s7lig/acloud/setup/host_setup_runner.py", 
>> line 67, in ShouldRun
>> if not utils.IsSupportedPlatform():
>>   File "/tmp/Soong.python_ym5s7lig/acloud/internal/lib/utils.py", line 
>> 1218, in IsSupportedPlatform
>> dist = platform.linux_distribution()[0]
>>
>>
>>
>> Why does acloud seemingly always use the latest python version on the 
>> system (3.8.2 in my case) rather than the one set to local python? 
>> (platform.linux_distribution API has been removed in Python 3.8)
>>
>> Building and running acloud-dev worked around this issue, but I needed to 
>> ensure that python2 was the active version on my system.
>>
>>
>>
>>
>>

-- 
-- 
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/8d35a288-8be5-4623-8032-637b61851601o%40googlegroups.com.

[android-building] Re: android build take eons

['Glenn Kasten' via Android Building]

The listed build hardware requirements 
 
are the bare minimum.
The more RAM and CPUs you have, the better.
And be sure to use make -k to take advantage of all your CPUs.

On Monday, May 4, 2020 at 12:19:43 PM UTC-7, Imx6dev Kit wrote:
>
> I got my AOSP build to work but it took maybe 8 hours ... i cannot imagine 
> how anyone can develop anything this way .. if i want to include a new 
> library, or write a new driver, or change something minimal, and recompile, 
> isn't there a way to do it quicker?  What is the recommended way to build 
> after making a minor change?
>

-- 
-- 
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/5192f89b-c40e-4bba-969c-ec6f012d8324%40googlegroups.com.

[android-building] Re: Finding corresponding pixel kernel in msm repo for a given released android version

['Glenn Kasten' via Android Building]

I don't know the answer to your specific question, but here are some 
general resources that might help:
https://source.android.com/setup/build/building-kernels
https://source.android.com/devices/architecture/kernel/android-common

On Monday, May 4, 2020 at 8:48:53 AM UTC-7, Zheng Zhang wrote:
>
> Hi:
> I'm a student trying to compile Android kernel with kcov. How could I 
> find pixel kernel  (in kernel/msm repo) corresponding to a specific Android 
> version? 
> For example, how could I find a kernel snapshot in the kernel/msm 
> repository that corresponds to QQ2A.200405.005? It seems that tag in 
> Android(android-10.0.0_r33) is different from the tag in MSM repository 
> (android-10.0.0_r0.33, for example). Could you give me any suggestions?
> Thanks very much!
>

-- 
-- 
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/e294a2d2-06b6-4e0d-be8b-212bcf8c90eb%40googlegroups.com.

[android-building] Re: Android 10 Released

['Glenn Kasten' via Android Building]

There is another thread on a similar topic.
Please see my reply there:

   Finding corresponding pixel kernel in msm repo for a given released 
android version
  https://groups.google.com/forum/#!topic/android-building/ziIidQ4UcLw


On Monday, May 4, 2020 at 8:48:45 AM UTC-7, Zheng Zhang wrote:
>
> Hi, Dr Xin Li:
>I'm a student trying to compile Android kernel with kcov. How could 
> I find corresponding pixel kernel  (in kernel/msm repo) for a specific 
> Android version? 
>For example, how could I find a kernel snapshot in the kernel/msm 
> repository that corresponds to QQ2A.200405.005? It seems that tag in 
> Android(android-10.0.0_r33) is different from the tag in MSM repository 
> (android-10.0.0_r0.33, for example). Could you give me any suggestions?
>Thanks very much!
>   
>  zheng zhang
>
> On Monday, April 6, 2020 at 7:36:52 PM UTC-7, Xin Li wrote:
>>
>> Hi all,
>>
>> Android 10 source code is now available. The following builds, tags, and 
>> devices are supported:
>>  - QQ2A.200405.005, android-10.0.0_r33, Pixel 2, Pixel 2 XL, Pixel 3, 
>> Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL
>>
>> The corresponding factory images, ota images, and proprietary binaries 
>> are available at
>>
>>   https://developers.google.com/android/images
>>   https://developers.google.com/android/ota
>>   https://developers.google.com/android/drivers
>>
>> We also pushed the corresponding kernel projects for the following 
>> devices:
>>
>> Tag  | Project | Branch  
>> | Device
>> android-10.0.0_r0.50 | kernel/msm  | 
>> android-msm-wahoo-4.4-android10 | Pixel 2 XL, Pixel 2
>> android-10.0.0_r0.51 | kernel/arm64| 
>> android-amber-intel-linux-4.7-android10 | Pixel 2 XL, Pixel 2
>> android-10.0.0_r0.52 | kernel/msm  | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-extra| 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/qcacld   | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.52 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-crosshatch-4.9-android10| Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.53 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 3 XL, Pixel 3
>> android-10.0.0_r0.54 | kernel/msm  | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-extra| 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/qcacld   | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.54 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-bonito-4.9-android10| Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.55 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 3a XL, Pixel 3a
>> android-10.0.0_r0.56 | kernel/msm  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-extra| 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/data-kernel  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/fts_touch| 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/qca-wfi-host-cmn | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/qcacld   | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.56 | kernel/msm-modules/wlan-fw-api  | 
>> android-msm-coral-4.14-android10| Pixel 4 XL, Pixel 4
>> android-10.0.0_r0.57 | kernel/arm64| 
>> android-blue-intel-linux-4.7-android10  | Pixel 4 XL, Pixel 4
>>
>

-- 
-- 
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 

[android-building] Re: Build processes uses 100% CPU and >4GB RAM all time, crashes frequently during build

['Glenn Kasten' via Android Building]

> Not sure if my hardware meets the requeriments for AOSP builds.
see 
https://source.android.com/setup/build/requirements#hardware-requirements
for minimums but it is better to have much more

On Saturday, March 14, 2020 at 11:58:40 AM UTC-7, Eliane Fonseca wrote:
>
> During the builds, using somewhat underpowered hardware (1 GHz CPU, 8GB 
> RAM, no SSD), the build process uses 100% CPU and a large RAM amount, 
> different AOSP versions tried (7.1, 8.0, 9, 10) , and my CPU stays at 1.00 
> GHz rather than auto overclocking (it can, up to 1.40 GHz). Long running 
> builds frequently crashes as well but simply running make again allows the 
> build to proceed. Not sure if my hardware meets the requeriments for AOSP 
> builds.
>

-- 
-- 
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/b8e12230-5df6-4beb-8354-0ffe8fdac6c4%40googlegroups.com.

[android-building] Re: Error during building AOSP for Moto G5s Plus

['Glenn Kasten' via Android Building]

I just noticed that this discussion thread is about a build target that is 
unsupported by AOSP,
therefore this thread is off-topic for the android-building group.  As long 
as only upstream AOSP is involved,
then you can post about unsupported build targets at android-porting group.
However, if other components beyond AOSP are involved, then it would also 
be off-topic for android-porting.
Please see posting guidelines at top of:
https://groups.google.com/forum/?oldui=1#!forum/android-building
https://groups.google.com/forum/?oldui=1#!forum/android-porting

On Thursday, March 12, 2020 at 7:55:51 PM UTC-7, Andrew Wheeler wrote:
>
> Are you adding components from LineageOS?  Maybe you need to port this 
> 
> ?
>
>
> On Thursday, March 12, 2020 at 12:21:46 PM UTC-5, Rajesh Kumbhakar wrote:
>>
>> FAILED: ninja: 
>> 'out/target/product/sanders/obj/HEADER_LIBRARIES/generated_kernel_headers_intermediates/export_includes',
>>  
>> needed by 
>> 'out/target/product/sanders/obj/STATIC_LIBRARIES/libwifi-hal-qcom_intermediates/import_includes',
>>  
>> missing and no known rule to make it
>>
>> can anyone help me with this please...?
>>
>

-- 
-- 
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/b4d19fab-5ea1-4aff-996c-d79053a50f73%40googlegroups.com.

[android-building] Re: Compile AOSP on Intel Platforms

['Glenn Kasten' via Android Building]

> for an old Tablet with Intel Atom Z2520

Sorry, this post got past moderation and should have been redirected to 
android-porting.
The device mentioned is not an AOSP-supported build target.
See the list of AOSP-supported build targets 
.

Please post follow-ups to android-porting, not here
Thank you

On Thursday, January 30, 2020 at 7:06:27 AM UTC-8, Agostinho Carvalho wrote:
>
> I'm trying to compile AOSP 10 for an old Tablet with Intel Atom Z2520 
> (32-bit architecture).
>
> Question 1: What lunch option should I use, to compile for that Tablet + 
> SoC combination?
>
> Current offered options are:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_blueline-userdebug
>  4. aosp_bonito-userdebug
>  5. aosp_car_arm-userdebug
>  6. aosp_car_arm64-userdebug
>  7. aosp_car_x86-userdebug
>  8. aosp_car_x86_64-userdebug
>  9. aosp_cf_arm64_phone-userdebug
>  10. aosp_cf_x86_64_phone-userdebug
>  11. aosp_cf_x86_auto-userdebug
>  12. aosp_cf_x86_phone-userdebug
>  13. aosp_cf_x86_tv-userdebug
>  14. aosp_coral-userdebug
>  15. aosp_crosshatch-userdebug
>  16. aosp_flame-userdebug
>  17. aosp_marlin-userdebug
>  18. aosp_sailfish-userdebug
>  19. aosp_sargo-userdebug
>  20. aosp_taimen-userdebug
>  21. aosp_walleye-userdebug
>  22. aosp_walleye_test-userdebug
>  23. aosp_x86-eng
>  24. aosp_x86_64-eng
>  25. beagle_x15-userdebug
>  26. fuchsia_arm64-eng
>  27. fuchsia_x86_64-eng
>  28. hikey-userdebug
>  29. hikey64_only-userdebug
>  30. hikey960-userdebug
>  31. hikey960_tv-userdebug
>  32. hikey_tv-userdebug
>  33. m_e_arm-userdebug
>  34. mini_emulator_arm64-userdebug
>  35. mini_emulator_x86-userdebug
>  36. mini_emulator_x86_64-userdebug
>  37. poplar-eng
>  38. poplar-user
>  39. poplar-userdebug
>  40. qemu_trusty_arm64-userdebug
>  41. uml-userdebug
>
>
>
>
>
> Question 2: Although the list provided above offers lots of options, it 
> doesn't list them all.
> Is there a way to list every single option?
>
>
>
>
>
> Question 3: Android on Intel Platform seems to have renamed to "Project 
> Celadon".
> So I tried using the following manifest:
> repo init -u 
> https://github.com/projectceladon/manifest/blob/master/default.xml
> I'm not sure if this Celadon manifest is the one I need for my Intel 
> Tablet.
>
>
> Even if I use the lunch combination "celadon-user" I still get the 
> following error:
>
> ...
> ...
> ...
> ...
>
> Skipped fetching project platform/hardware/qcom/msm8998 (already have 
> persistent ref)
> Skipped fetching project device/google/marlin-kernel (already have 
> persistent ref)
> Skipped fetching project platform/test/vts-testcase/hal (already have 
> persistent ref)
> Skipped fetching project platform/external/f2fs-tools (already have 
> persistent ref)
> Skipped fetching project platform/tools/security (already have persistent 
> ref)
> Skipped fetching project platform/external/python/httplib2 (already have 
> persistent ref)
> Skipped fetching project platform/external/libhevc (already have 
> persistent ref)
> Fetching projects:  99% (796/804) platform/external/python/httplib2Skipped 
> fetching project platform/frameworks/opt/setupwizard (already have 
> persistent ref)
> Skipped fetching project device/generic/car (already have persistent ref)
> Skipped fetching project platform/external/iperf3 (already have 
> persistent ref)
> Skipped fetching project platform/packages/apps/CertInstaller (already 
> have persistent ref)
> Skipped fetching project platform/tools/apkzlib (already have persistent 
> ref)
> Fetching projects: 100% (804/804), done.
> Checking out projects:   4% (33/803) device/generic/x86_64error: Cannot 
> checkout device/google/bonito-kernel: GitError: device/google/bonito-kernel 
> rev-list ('^eebd2aa4f12a59eec71188a59f5b67a1d9418251', 'HEAD', '--'): 
> fatal: bad object HEAD
>
> Traceback (most recent call last):
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 530, in 
> 
> _Main(sys.argv[1:])
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 505, in 
> _Main
> result = run()
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 498, in 
> 
> run = lambda: repo._Run(name, gopts, argv) or 0
>   File "/home/agostinho/AOSP/Build1/.repo/repo/main.py", line 201, in _Run
> result = cmd.Execute(copts, cargs)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 994, 
> in Execute
> self._Checkout(all_projects, opt)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 553, 
> in _Checkout
> self._CheckoutWorker(**kwargs)
>   File "/home/agostinho/AOSP/Build1/.repo/repo/subcmds/sync.py", line 435, 
> in _CheckoutWorker
> return self._CheckoutOne(opt, project, *args, **kwargs)
>   File 

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

This is most likely due to insufficient RAM (8 GB).
I'll request that this page be updated:
https://source.android.com/setup/build/requirements

On Wednesday, January 8, 2020 at 12:01:10 PM UTC-8, Eliane Fonseca wrote:
>
> [ 15% 13954/87886] target  C++: libLLVM_swiftshader <= 
> external/swiftshader/third_party/llvm-7.0/llvm/lib
> FAILED: 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
> /bin/bash -c "PWD=/proc/self/cwd  
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++ -I bionic -I 
> external/swiftshader/third_party/llvm-7.0/llvm/include -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/AArch64 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/ARM -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/configs/android/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/IR -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/AArch64 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/ARM 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/X86 
> -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Transforms/InstCombine
>  
> -I external/swiftshader/third_party/llvm-7.0 -I 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> -I 
> out/target/product/generic_x86/gen/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> \$(cat 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/import_includes)
>
> -isystem out/target/product/generic_x86/obj/include -c  -msse3 
> -mstackrealign -DANDROID -fmessage-length=0 -W -Wall -Wno-unused 
> -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG 
> -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing 
> -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof 
> -faddrsig -Wimplicit-fallthrough -Werror=int-conversion 
> -Wno-reserved-id-macro -Wno-format-pedantic 
> -Wno-unused-command-line-argument -fcolor-diagnostics 
> -Wno-zero-as-null-pointer-constant -Wno-sign-compare 
> -Wno-defaulted-function-deleted -Wno-inconsistent-missing-override 
> -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables 
> -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 
> -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor 
> -Werror=address -Werror=sequence-point -Werror=date-time 
> -Werror=format-security -nostdlibinc -m32 -march=prescott -target 
> i686-linux-android 
> -Bprebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/x86_64-linux-android/bin
>   
> -Wsign-promo -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS 
> -Wno-thread-safety-negative -Wno-gnu-include-next 
> -fvisibility-inlines-hidden  -std=gnu++17   -fno-rtti 
> -DLOG_TAG=\\\"libLLVM_swiftshader\\\" -Wall -Werror 
> -Wno-implicit-exception-spec-mismatch -Wno-overloaded-virtual 
> -Wno-undefined-var-template -Wno-unneeded-internal-declaration 
> -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef 
> -Wno-unused-parameter -Wno-unused-private-field -Wno-unused-variable 
> -Wno-unknown-warning-option -Xclang -fuse-init-array -Os 
> -fomit-frame-pointer -ffunction-sections -fdata-sections 
> -fno-operator-names -msse2 -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -DANDROID_PLATFORM_SDK_VERSION=29 -U_FORTIFY_SOURCE -D__ANDROID_API__=29 
> -D__ANDROID_VNDK__ -fPIC -Wno-enum-compare -Wno-enum-compare-switch 
> -Wno-null-pointer-arithmetic -Wno-null-dereference -D_USING_LIBCXX 
> -std=c++11  -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast 
> -Werror=address-of-temporary -Werror=return-type 
> -Wno-tautological-constant-compare -Wno-tautological-type-limit-compare 
> -Wno-tautological-unsigned-enum-zero-compare 
> -Wno-tautological-unsigned-zero-compare -Wno-c++98-compat-extra-semi 
> -Wno-return-std-move-in-c++11  -MD -MF 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.d
>  
> -o 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
>  
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Analysis/SyntheticCountsUtils.cpp"
> Stack dump:
> 0.Program arguments: 
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++.real -cc1 -triple 
> i686-unknown-linux-android -emit-obj -mnoexecstack -disable-free 
> -disable-llvm-verifier -discard-value-names -main-file-name 
> SyntheticCountsUtils.cpp -mrelocation-model pic -pic-level 2 -mthread-model 
> posix -relaxed-aliasing -masm-verbose -mconstructor-aliases -munwind-tables 
> -fuse-init-array -target-cpu prescott 

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

Thank you.  I have filed an internal bug and will plan to get back to you 
if they request additional information.

On Wednesday, January 8, 2020 at 1:06:12 PM UTC-8, Eliane Fonseca wrote:
>
> Below is the hardware/build config
>
> Release branch: android10-qpr1-release, android-10.0.0_r15, Build target: 
> aosp_x86-eng, command: m -j2, Host: Ubuntu 18.04 64 bit, Hardware config: 
> AMD C-60 CPU (2 cores, 1.00 GHz)/8 GB RAM/285 GB storage. This happened 
> today after 2+ hours building. Not sure if it was insufficient RAM or high 
> CPU usage.
>

-- 
-- 
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/7ba4884d-904e-4fa3-9384-56a3b9c1558f%40googlegroups.com.

[android-building] Re: Building android-10.0.0_r15 segmentation fault error

['Glenn Kasten' via Android Building]

Thank you for reporting this.
Can you please mention which branch you synced, the lunch command, the 
top-level make command you used, the host OS and hardware configuration, 
and any other information that might help to reproduce or investigate (for 
example, whether this is a new problem and what changed recently, etc.)?

On Wednesday, January 8, 2020 at 12:01:10 PM UTC-8, Eliane Fonseca wrote:
>
> [ 15% 13954/87886] target  C++: libLLVM_swiftshader <= 
> external/swiftshader/third_party/llvm-7.0/llvm/lib
> FAILED: 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
> /bin/bash -c "PWD=/proc/self/cwd  
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++ -I bionic -I 
> external/swiftshader/third_party/llvm-7.0/llvm/include -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/AArch64 -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/ARM -I 
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/X86 -I 
> external/swiftshader/third_party/llvm-7.0/configs/android/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/include -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/IR -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/AArch64 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/ARM 
> -I external/swiftshader/third_party/llvm-7.0/configs/common/lib/Target/X86 
> -I 
> external/swiftshader/third_party/llvm-7.0/configs/common/lib/Transforms/InstCombine
>  
> -I external/swiftshader/third_party/llvm-7.0 -I 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> -I 
> out/target/product/generic_x86/gen/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates
>  
> \$(cat 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/import_includes)
>
> -isystem out/target/product/generic_x86/obj/include -c  -msse3 
> -mstackrealign -DANDROID -fmessage-length=0 -W -Wall -Wno-unused 
> -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG 
> -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing 
> -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof 
> -faddrsig -Wimplicit-fallthrough -Werror=int-conversion 
> -Wno-reserved-id-macro -Wno-format-pedantic 
> -Wno-unused-command-line-argument -fcolor-diagnostics 
> -Wno-zero-as-null-pointer-constant -Wno-sign-compare 
> -Wno-defaulted-function-deleted -Wno-inconsistent-missing-override 
> -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables 
> -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 
> -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor 
> -Werror=address -Werror=sequence-point -Werror=date-time 
> -Werror=format-security -nostdlibinc -m32 -march=prescott -target 
> i686-linux-android 
> -Bprebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.9/x86_64-linux-android/bin
>   
> -Wsign-promo -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS 
> -Wno-thread-safety-negative -Wno-gnu-include-next 
> -fvisibility-inlines-hidden  -std=gnu++17   -fno-rtti 
> -DLOG_TAG=\\\"libLLVM_swiftshader\\\" -Wall -Werror 
> -Wno-implicit-exception-spec-mismatch -Wno-overloaded-virtual 
> -Wno-undefined-var-template -Wno-unneeded-internal-declaration 
> -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef 
> -Wno-unused-parameter -Wno-unused-private-field -Wno-unused-variable 
> -Wno-unknown-warning-option -Xclang -fuse-init-array -Os 
> -fomit-frame-pointer -ffunction-sections -fdata-sections 
> -fno-operator-names -msse2 -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -DANDROID_PLATFORM_SDK_VERSION=29 -U_FORTIFY_SOURCE -D__ANDROID_API__=29 
> -D__ANDROID_VNDK__ -fPIC -Wno-enum-compare -Wno-enum-compare-switch 
> -Wno-null-pointer-arithmetic -Wno-null-dereference -D_USING_LIBCXX 
> -std=c++11  -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast 
> -Werror=address-of-temporary -Werror=return-type 
> -Wno-tautological-constant-compare -Wno-tautological-type-limit-compare 
> -Wno-tautological-unsigned-enum-zero-compare 
> -Wno-tautological-unsigned-zero-compare -Wno-c++98-compat-extra-semi 
> -Wno-return-std-move-in-c++11  -MD -MF 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.d
>  
> -o 
> out/target/product/generic_x86/obj/STATIC_LIBRARIES/libLLVM_swiftshader_intermediates/llvm/lib/Analysis/SyntheticCountsUtils.o
>  
> external/swiftshader/third_party/llvm-7.0/llvm/lib/Analysis/SyntheticCountsUtils.cpp"
> Stack dump:
> 0.Program arguments: 
> prebuilts/clang/host/linux-x86/clang-r353983c/bin/clang++.real -cc1 -triple 
> i686-unknown-linux-android -emit-obj -mnoexecstack -disable-free 
> -disable-llvm-verifier -discard-value-names -main-file-name 
> 

[android-building] Re: Pixel2 AOSP build No default GApps(playstore, gmail, chrome etc)

['Glenn Kasten' via Android Building]

Sorry proprietary apps and services are off-topic for android-building. 
Please read the guidelines at top of
   https://groups.google.com/forum/#!forum/android-building
in particular:
   "add-on applications and proprietary services not included in the AOSP 
platform distribution"



On Monday, January 6, 2020 at 10:27:24 AM UTC-8, sachin verma wrote:
>
> I have flashed android 10 aosp_walleye-userdebug in my Pixel2 device but I 
> could not find the default applications playstore, gmail, chrome etc(while 
> I had run the google and qualcom driver binaries script before creating 
> build).
>
> Is it disabled in the AOSP build?
>
> How can i enable or install the correct versions on flashed Custom ROM.
>
> Thanks,
> Sachin
>

-- 
-- 
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/131367e7-b05d-4a62-ac5c-2d63096f6389%40googlegroups.com.

[android-building] Re: Building Android GSI with Google Apps

['Glenn Kasten' via Android Building]

This topic slipped through moderation and should not have been approved for 
posting;
see guidelines at top of 
https://groups.google.com/forum/#!forum/android-building
in particular item #3 "add-on applications and proprietary services not 
included in the AOSP platform distribution".

On Thursday, December 19, 2019 at 8:31:49 AM UTC-8, Nisarg Ujjainkar wrote:
>
> Hi All, 
>
> I have successfully built and booted Android 9 GSI but it lacks the Google 
> apps. How can I build a GSI with the Google apps included?

-- 
-- 
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/e87386e0-6865-4b6a-92e1-af5245c4dae2%40googlegroups.com.

[android-building] Re: LineageOS 17.0 build in LXC 2.x - nsjail/sandboxing error

['Glenn Kasten' via Android Building]

Can you reproduce this problem with AOSP distribution?
This discussion group is targeted at AOSP distribution per guidelines here 
.
[I am a volunteer moderator]

On Tuesday, October 22, 2019 at 9:08:28 AM UTC-7, Condor wrote:
>
> Hello,
>
> I've just tried building LineageOS 17.0 for fajita (OnePlus 6T). For 
> efficiency reasons and to maintain isolation from the host I've opted to 
> spin up an LXC container for this.
> The host machine is running Debian 9 and LXC 2.x, while the container is a 
> Debian 10 machine. Apparently this doesn't support nsjail, which caused 
> "breakfast fajita" to fail.
> A screenshot is available at 
> https://www.nixmagic.com/pics/lineage-nsjail-error.png.
> I've followed the build guide at 
> https://wiki.lineageos.org/devices/fajita/build.
> Below is the error log in text form.
>
> Looking for dependencies in kernel/oneplus/sdm845
> kernel/oneplus/sdm845 has no additional dependencies.
> Looking for dependencies in packages/resources/devicesettings 
> packages/resources/devicesettings has no additional dependencies.
> Done
> 15:31:05 Build sandboxing disabled due to nsjail error. This may become 
> fatal in the future.
> 15:31:05 Please let us know why nsjail doesn't work in your environment at:
> 15:31:05 https://groups.google.com/forum/#!forum/android-building
> 15:31:05 https://issuetracker.google.com/issues/new?component=381517
> build/make/target/product/updatable_apex.mk:21: error: 
> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]: 
> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
> 15:31:11 dumpvars failed with: exit status 1
> 15:31:13 Build sandboxing disabled due to nsjail error. This may become 
> fatal in the future.
> 15:31:13 Please let us know why nsjail doesn't work in your environment at:
> 15:31:13 https://groups.google.com/forum/#!forum/android-building
> 15:31:13 https://issuetracker.google.com/issues/new?component=381517
> build/make/target/product/updatable_apex.mk:21: error: 
> _nic.PRODUCTS.[[device/oneplus/fajita/lineage_fajita.mk]]: 
> "vendor/oneplus/sdm845-common/sdm845-common-vendor.mk" does not exist.
> 15:32:42 dumpvars failed with: exit status 1
>
> ** Don't have a product spec for: 'lineage_fajita'
> ** Do you have the right repo manifest? 
>
> I wish I could explain why nsjail isn't available in LXC but unfortunately 
> I don't know either... I'll retry the build in a VM or on a physical host.
>
> Best regards,
> Michael De Roover (android-building at nixmagic dot 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/b8113ccb-73b0-4c6f-8cea-1cd29768f8e4%40googlegroups.com.

Re: [android-building] Re: Error when building Reference TV App

['Glenn Kasten' via Android Building]

Please see the second paragraph of
https://source.android.com/setup/community#for-business-inquiries
that starts "While we read ...". 

On Thursday, August 1, 2019 at 7:23:58 PM UTC-7, jw wang wrote:
>
>
> Hi Nick
>
> what do you mean for "partner engineering source " ?
>
> is it a android Q pre aosp that available for the pixel device, I mean, 
> I'm looking for some way to get a pre-Q AOSP that I'm able to build Q 
> userdebug image for my pixels, 
>
> so I can start some migration of the project inside framework (no source 
> code available in androidsource for general public) on the upcoming OS, 
>
> I've tried to write to android-partnersh...@google.com but end up 
> nothing, can you give me some clue ?
>
>
>
>
>
>
> On Friday, 2 August 2019 03:12:01 UTC+8, Nick Chalko wrote:
>>
>> Sorry about that.  
>>
>>
>> I have verified that my latest internal version build on Q.
>> I am working with my build team to get the source on Q updated and that 
>> will be released to public when Q is released.
>>
>> Meanwhile do you have access to partner engineering source ?
>>
>>
>> On Thu, Aug 1, 2019 at 7:54 AM Haris Zukanović  
>> wrote:
>>
>>> I tried building today... it still does not work...
>>> Any updates to expect soon?
>>>
>>> -- 
>>> -- 
>>> 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 a topic in the 
>>> Google Groups "Android Building" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/android-building/f6aGR9qo9WI/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> android-...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/android-building/6fea0bfe-0e69-43ad-a4ed-327d74f7a576%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Nick Chalko | Software Engineer | nch...@google.com |   :-) 
>> Generate your java flags for easier testing.
>> go/java-flags-generator
>>
>

-- 
-- 
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/8b1c51de-e13d-4d2f-9f1b-fa6022052e59%40googlegroups.com.

Re: [android-building] Re: No files in working folder after running repo sync

['Glenn Kasten' via Android Building]

Yes it looks like the DNS lookup failed: Could not resolve host: 
android.googlesource.com
but strange that it succeeded earlier. As you mentioned, perhaps try again.

On Wednesday, July 24, 2019 at 4:02:09 PM UTC-7, Lord Unknown wrote:
>
> Hi Glenn,
>
> Here's all the errors in repo sync: https://hastebin.com/quxuwumexo
> repo init did not output any errors.
>
> Here's the full output: https://hastebin.com/locubibaju 
> <https://hastebin.com/locubibaju.>
>
> The internet connection was a bit slow today. Maybe that's the issue.
>
> Thank you in advance,
> - Michael
>
> On Wed, Jul 24, 2019 at 8:23 PM 'Glenn Kasten' via Android Building <
> android-building@googlegroups.com> wrote:
>
>> Can you please include a short excerpt of just any errors in the output 
>> of the repo init and sync?
>>
>> On Wednesday, July 24, 2019 at 10:20:52 AM UTC-7, Lord Unknown wrote:
>>>
>>> Hi everyone,
>>>
>>> I ran repo init and repo sync in /vagrant/android (I'm running Ubuntu 
>>> 14.04 in Vagrant). I ran ls in /vagrant/android and there were no folders, 
>>> except .repo
>>>
>>> What could happen with folders? And how to solve this problem?
>>>
>>> The commands that I've used: 
>>> repo init -u https://android.googlesource.com/platform/manifest -b 
>>> android-9.0.0_r45 -p linux --depth=1
>>> repo sync -j9
>>>
>>> Regards,
>>> - 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/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/android-building/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
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/3b5b5352-a0cd-4ba6-affb-e31dc113c91e%40googlegroups.com.

[android-building] Re: No files in working folder after running repo sync

['Glenn Kasten' via Android Building]

Can you please include a short excerpt of just any errors in the output of 
the repo init and sync?

On Wednesday, July 24, 2019 at 10:20:52 AM UTC-7, Lord Unknown wrote:
>
> Hi everyone,
>
> I ran repo init and repo sync in /vagrant/android (I'm running Ubuntu 
> 14.04 in Vagrant). I ran ls in /vagrant/android and there were no folders, 
> except .repo
>
> What could happen with folders? And how to solve this problem?
>
> The commands that I've used: 
> repo init -u https://android.googlesource.com/platform/manifest -b 
> android-9.0.0_r45 -p linux --depth=1
> repo sync -j9
>
> Regards,
> - 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/b06387f6-81e5-4d84-a825-f3687ae88979%40googlegroups.com.

[android-building] Re: Error when build Android Q Beta5 for Pixel3

['Glenn Kasten' via Android Building]

The previews are not intended to be buildable, they are for reference only.

See this post:
GPL projects for Android Q Beta 5
https://groups.google.com/forum/#!topic/android-building/uXXzjIqvER8

On Wednesday, July 24, 2019 at 6:01:54 AM UTC-7, Phuoc Nguyen wrote:
>
> Dear All,
> I am trying to build Android Q Beta5 for Pixel3 but the error occurred. 
> Could you shed me some light?
> Thanks
> Phuoc
>
>  abc@abc-283:~/Downloads/WORKING_DIRECTORY$ source build/envsetup.sh
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ lunch
>
> You're building on Linux
>
> Lunch menu... pick a combo:
>  1. aosp_arm-eng
>  2. aosp_arm64-eng
>  3. aosp_blueline-userdebug
>  4. aosp_car_arm-userdebug
>  5. aosp_car_arm64-userdebug
>  6. aosp_car_x86-userdebug
>  7. aosp_car_x86_64-userdebug
>  8. aosp_cf_arm64_phone-userdebug
>  9. aosp_cf_x86_64_phone-userdebug
>  10. aosp_cf_x86_auto-userdebug
>  11. aosp_cf_x86_phone-userdebug
>  12. aosp_cf_x86_tv-userdebug
>  13. aosp_crosshatch-userdebug
>  14. aosp_walleye-userdebug
>  15. aosp_walleye_test-userdebug
>  16. aosp_x86-eng
>  17. aosp_x86_64-eng
>  18. beagle_x15-userdebug
>  19. hikey-userdebug
>  20. hikey64_only-userdebug
>  21. hikey960-userdebug
>  22. hikey960_tv-userdebug
>  23. hikey_tv-userdebug
>  24. m_e_arm-userdebug
>  25. mini_emulator_arm64-userdebug
>  26. mini_emulator_x86-userdebug
>  27. mini_emulator_x86_64-userdebug
>  28. poplar-eng
>  29. poplar-user
>  30. poplar-userdebug
>  31. qemu_trusty_arm64-userdebug
>  32. uml-userdebug
>
> Which would you like? [aosp_arm-eng] aosp_blueline-userdebug
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.8.0-59-generic-x86_64-Ubuntu-16.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QP1A.190711.002
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av 
> hardware/google/interfaces hardware/google/pixel hardware/qcom/sdm845 
> vendor/google/camera vendor/qcom/sdm845 vendor/google/interfaces
> 
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ make -j4
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=10
> TARGET_PRODUCT=aosp_blueline
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=arm64
> TARGET_ARCH_VARIANT=armv8-a
> TARGET_CPU_VARIANT=generic
> TARGET_2ND_ARCH=arm
> TARGET_2ND_ARCH_VARIANT=armv8-a
> TARGET_2ND_CPU_VARIANT=generic
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-4.8.0-59-generic-x86_64-Ubuntu-16.10
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=QP1A.190711.002
> OUT_DIR=out
> PRODUCT_SOONG_NAMESPACES=device/google/crosshatch hardware/google/av 
> hardware/google/interfaces hardware/google/pixel hardware/qcom/sdm845 
> vendor/google/camera vendor/qcom/sdm845 vendor/google/interfaces
> 
> [100% 1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
> FAILED: out/soong/build.ninja
> 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
> error: device/google/wahoo/Android.bp:1:1: module "soong_namespace": 
> namespace hardware/google/pixel does not exist
> 08:28:15 soong bootstrap failed with: exit status 1
>
>  failed to build some targets (2 seconds) 
>
> abc@abc-283:~/Downloads/WORKING_DIRECTORY$ 
>
>

-- 
-- 
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/8be01e34-1ece-4582-8238-c2211d196c27%40googlegroups.com.

[android-building] Re: Q-preview AOSP availability ?

['Glenn Kasten' via Android Building]

The previews are not intended to be buildable, they are for reference only.

On Monday, July 1, 2019 at 8:05:52 AM UTC-7, jw wang wrote:
>
> Hello google
>
> is it possible that we can repo sync Q-preview AOSP, and build the 
> userdebug version into pixel 3a ?
> now the preview are mostly used to test API level, but when it comes to 
> testing the component compatibility under native layer for example
> frameworks/av/service/audioflinger, this obvious need a right aosp and 
> userdebug privilege to do so.
>
> I can see there so far are many Q-preview tags 
>
> https://android.googlesource.com/platform/frameworks/av/+/refs/tags/android-q-preview-4/services/audioflinger/
>
> but according to the experience in past few years, this ends up totally 
> different to the formal release..
>
> which branch in the current aosp git resemble the Q preview most ??
>
> is it the master branch repo init -u 
> https://android.googlesource.com/platform/manifest???
>
> 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/89377bb6-9d19-4501-82a4-88d3e5e07e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: GPL projects for Android Q Beta 4

['Glenn Kasten' via Android Building]

This preview is not intended to be buildable, it is for reference only.

On Sunday, June 16, 2019 at 7:47:45 PM UTC-7, Paulo Costa wrote:
>
> I found this problem too, and for once the fix was exactly what the error 
> suggested: 
>
> LPF + F2FS_SLOT_LEN -> [F2FS_SLOT_LEN] 
>
> However, there are other compilation errors after this one -- I gave up 
> before I could get to the end of a full compilation. 
>
> Also, the tag doesn't have many of the Q's changes -- particularly in 
> framework, most of the new APIs are missing, which makes it kind of useless 
> :/ 
>
> I ended extracting framework.jar from a Q beta 4 device and decompiling it 
> with dex2jar.

-- 
-- 
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/ebe6d4bf-67c4-4ebd-a375-3ff600b98f79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: AOSP libselinux build error for android-q-preview-1

['Glenn Kasten' via Android Building]

Reminder: see March 14 post. It still applies:

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

On Thursday, June 6, 2019 at 2:41:09 PM UTC-7, Paulo Costa wrote:
>
> Same problem here building Beta 4 (And beta 2.5 before)
>
> Did you ever figure it out?
>
> On Monday, May 20, 2019 at 12:30:07 PM UTC-3, Jean-Marc GRIMAUD wrote:
>>
>> Hi,
>> I now try to build android-q-preview-2.5, and have the following error:
>> error: cts/hostsidetests/jdwptunnel/Android.bp:15:1: 
>> "CtsJdwpTunnelHostTestCases" depends on undefined module "jdi-support"
>>
>> Any idea how to solve it ?
>> thanks in advance !
>>
>

-- 
-- 
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/c9ebb4de-6bbb-44be-a390-f89b75e8aaa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-building] Re: Why did you name it Soong, Kati, Ninja ?

['Glenn Kasten' via Android Building]

Kati  and Soong 
 appear to be from 
Star Trek.
I assume that Ninja comes from here 
 
:-)

On Tuesday, May 14, 2019 at 10:13:28 PM UTC-7, CK RYU wrote:
>
> Hi,
>
>  
>
> I have question about the soong build system.
>
>  
>
> I want to know why did you name it Soong, Kati, Ninja?
>
> Is the name meaningful?'
>
>  
>
> Thanks,
>
>  
>
> CK.RYU
>

-- 
-- 
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/d8d519db-c921-41dc-b353-d92f0fbe1602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.