[android-building] Re: I get an error when building Android 12

2021-10-26 Thread Chang Kyo 
[current workaround]
a. disable ccache  (will impact compiling speed)
b. let ccache and AOSP source code to different partition (if your tmpfs 
bigger enough or you already had another partition)
c. mount --bind allow you put ccache and AOSP source code in the same 
partition.(reference: 
https://stackoverflow.com/questions/61923015/ccache-fails-with-read-only)

[root cause]
Need to check which commit cause it check this rule when AOSP building.
Because before Android 12, ccache files and AOSP source code in the same 
partition works fine.
If someone knowledge root case, please share with us.

Thanks a lot.
hamm157...@gmail.com 在 2021年10月14日 星期四下午1:44:18 [UTC+8] 的信中寫道：

> Hi,I want to build an Android12 but I get an error.
>
> *build/make/core/soong_config.mk:195 : 
> warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use 
> SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.*
> *build/make/core/soong_config.mk:196 : 
> warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use 
> SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.*
> **
> *PLATFORM_VERSION_CODENAME=REL*
> *PLATFORM_VERSION=12*
> *TARGET_PRODUCT=aosp_cf_x86_64_phone*
> *TARGET_BUILD_VARIANT=userdebug*
> *TARGET_BUILD_TYPE=release*
> *TARGET_ARCH=x86_64*
> *TARGET_ARCH_VARIANT=silvermont*
> *TARGET_2ND_ARCH=x86*
> *TARGET_2ND_ARCH_VARIANT=silvermont*
> *TARGET_2ND_CPU_VARIANT=silvermont*
> *HOST_ARCH=x86_64*
> *HOST_2ND_ARCH=x86*
> *HOST_OS=linux*
> *HOST_OS_EXTRA=Linux-5.11.0-37-generic-x86_64-Ubuntu-21.04*
> *HOST_CROSS_OS=windows*
> *HOST_CROSS_ARCH=x86*
> *HOST_CROSS_2ND_ARCH=x86_64*
> *HOST_BUILD_TYPE=release*
> *BUILD_ID=SP1A.210812.015*
> *OUT_DIR=out*
> *PRODUCT_SOONG_NAMESPACES=device/generic/goldfish-opengl 
> device/generic/goldfish-opengl hardware/google/camera 
> hardware/google/camera/devices/EmulatedCamera external/mesa3d 
> vendor/google_devices/common/pr*
> *oprietary/confirmatioui_hal*
> **
> *[ 98% 1194/1212] including system/sepolicy/Android.mk ...*
> *system/sepolicy/Android.mk:57: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR 
> has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.*
> *system/sepolicy/Android.mk:62: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR 
> has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.*
> *[  2% 3371/150039] target  C: ip-up-vpn <= 
> frameworks/native/cmds/ip-up-vpn/ip-up-vpn.c*
> *FAILED: 
> out/target/product/vsoc_x86_64/obj/EXECUTABLES/ip-up-vpn_intermediates/ip-up-vpn.o*
> */bin/bash -c "PWD=/proc/self/cwd /usr/bin/ccache 
> prebuilts/clang/host/linux-x86/clang-r416183b1/bin/clang -I 
> frameworks/native/cmds/ip-up-vpn -I 
> out/target/product/vsoc_x86_64/obj/EXECUTABLES/ip-up-vpn_i*
> *ntermediates -I 
> out/target/product/vsoc_x86_64/gen/EXECUTABLES/ip-up-vpn_intermediates 
> -Isystem/core/libcutils/include -Isystem/core/libprocessgroup/include 
> -Isystem/logging/liblog/include -Iexternal/lib*
> *cxx/include -Iexternal/libcxxabi/include -D__LIBC_API__=1 
> -Ibionic/libc/async_safe/include -Isystem/logging/liblog/include 
> -Ibionic/libc/system_properties/include 
> -Isystem/core/property_service/libpr*
> *opertyinfoparser/include -isystem bionic/libc/include -isystem 
> bionic/libc/kernel/uapi -isystem bionic/libc/kernel/android/scsi -isystem 
> bionic/libc/kernel/android/uapi -isystem bionic/libc/kernel/uapi/a*
> *sm-x86 -D__LIBM_API__=1 -D__LIBDL_API__=1 -isystem 
> bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem 
> bionic/libc/kernel/android/scsi -isystem bionic/libc/kernel/android/uapi 
> -isystem *
> *bionic/libc/kernel/uapi/asm-x86 -Iexternal/libcxxabi/include   -I 
> system/core/include -I system/logging/liblog/include -I 
> system/media/audio/include -I hardware/libhardware/include -I 
> hardware/libhardwar*
> *e_legacy/include -I hardware/ril/include -I frameworks/native/include -I 
> frameworks/native/opengl/include -I frameworks/av/include  -c  
> -Werror=implicit-function-declaration -DANDROID -fmessage-length=0 *
> *-W -Wall -Wno-unused -Winit-self -Wpointer-arith 
> -Wunreachable-code-loop-increment -no-canonical-prefixes -DNDEBUG -UDEBUG 
> -fno-exceptions -Wno-multichar -O2 -g -fdebug-info-for-profiling 
> -fno-strict-ali*
> *asing -Werror=date-time -Werror=pragma-pack 
> -Werror=pragma-pack-suspicious-include -Werror=string-plus-int 
> -Werror=unreachable-code-loop-increment -fdebug-prefix-map=/proc/self/cwd= 
> -D__compiler_offsetof*
> *=__builtin_offsetof -faddrsig -fcommon -Werror=int-conversion 
> -fexperimental-new-pass-manager -Wno-reserved-id-macro 
> -Wno-unused-command-line-argument -fcolor-diagnostics -Wno-sign-compare 
> -Wno-defaulted*
> *-function-deleted -Wno-inconsistent-missing-override -Wno-c99-designator 
> -Wno-gnu-folding-constant -Wunguarded-availability 
> -D__ANDROID_UNAVAILABLE_SYMBOLS_ARE_WEAK__ -ftrivial-auto-var-init=zero 
> -enable*
>

[android-building] Re: how to integrate ninja and RBE to support remote build AOSP so fast?

2020-09-14 Thread Chang Kyo 
Hi Joe:
I also want to know the detail about setup/use the RBE.

Does it mean if I have a lot of machine(virtual or physical),
I can separate the AOSP compile process on them?

Because as android version rising, the compile time rising also.
[image: aosp_11_compile_time.png]
i'm afraid it will impact our product develop time next year.

Thanks a lot.
Chang
Joe Hicks 在 2020年5月14日 星期四上午4:11:45 [UTC+8] 的信中寫道：

> Hi Yun,
>
> I will reach out directly to you to discuss.
>
> Thanks,
> Joe
>
> On Wednesday, May 13, 2020 at 3:24:55 PM UTC-4 Yun Ma wrote:
>
>> Hi Dan,
>>
>> Do we have more detail document about how to setup/use the RBE? We have 
>> interesting about this build feature.
>>
>> Thanks
>> Yun
>>
>> On Monday, March 23, 2020 at 9:19:51 PM UTC-7, Dan Willemsen wrote:
>>>
>>> Someone should be reaching out to you directly about RBE, but I'd like 
>>> to clarify that the remote execution API 
>>>  has more clients than just 
>>> Bazel (even though it is in the bazelbuild github organization). The 
>>> rewrapper support in AOSP is unrelated to Bazel, and currently integrates 
>>> with the build similarly to ccache -- as a compiler wrapper.
>>>
>>> - Dan
>>>
>>> On Monday, March 23, 2020 at 7:39:55 AM UTC-7 mooo...@gmail.com wrote:
>>>
 hi,

 Android Building group,

 I noticed that One PPT called "Remote Execution and Caching for Android 
 Platform" . 
 Inside it has one page , it shows that ninja can call re.warper to 
 execute clang/java on remote server.

 In that PPT it shows the result is quite good from my point of view. 
 So, I want to know how it works? how can i build one system like this? I 
 have read pages 
 https://cloud.google.com/remote-build-execution/docs/overview . I 
 learned that RBE is for Bazel .

 So I learned Bazel, I found that ,Bazel has its own BUILD file to be 
 the input to compile code. So I confused ,could any one can tell me ? How 
 does ninja call re-wrapper and send "compile" command to remote execution? 
 How does this progress know the out file is exist in Remote Cache? 


 I need to build one system like this to make the android and chips 
 driver compile as fast as I can. thanks

 [image: google.png]




-- 
-- 
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/80c2b419-81a3-44ea-92ee-5156a8a6140an%40googlegroups.com.

[android-building] Re: It is possible to build android 1.6 on ubuntu 18.04 ?

2019-12-09 Thread Chang Kyo 
Dear Eliane:
If you still develop android 1.6,
I'll suggest that you can using docker or singularity to build container 
image which include ubuntu 10.04 + Java SDK 5 + android 1.6 require package.
After that, you can build android 1.6 using container on any version OS 
which support docker or singularity.
F.Y.I.

Eliane Fonseca於 2019年12月9日星期一 UTC+8上午8時29分22秒寫道：
>
> Has anyone built android 1.6 (donut) on ununtu 18.04 without any errors? I 
> am trying to build it, but  it probably doesn't support jdk 1.8
>

-- 
-- 
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/bd8240e8-fcff-46ce-9674-64ebd9162b40%40googlegroups.com.