Re: [android-building] android-9.0.0_r8 build error

2020-11-09 Thread 'Dan Willemsen' via Android Building 
Did you sync to that from some other revision? The `repo` tool doesn't go
back and clean up "removed" / files when changing
manifests, so there's some number of dangling symlinks in your worktree. If
you remove the five files that it complains about, that's probably enough
to get it working.

- Dan

On Mon, Nov 9, 2020 at 8:13 AM Arthur Clark  wrote:

> this is output message:
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=9
> TARGET_PRODUCT=aosp_x86
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=x86
> TARGET_ARCH_VARIANT=x86
> HOST_ARCH=x86_64
> HOST_2ND_ARCH=x86
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-5.4.0-42-generic-x86_64-Ubuntu-18.04.5-LTS
> HOST_CROSS_OS=windows
> HOST_CROSS_ARCH=x86
> HOST_CROSS_2ND_ARCH=x86_64
> HOST_BUILD_TYPE=release
> BUILD_ID=PPR2.180905.006.A1
> OUT_DIR=out
> 
> [1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
> FAILED: out/soong/.bootstrap/build.ninja
> out/soong/.minibootstrap/minibp -t -l out/.module_paths/Android.bp.list -b
> out/soong -n out -d out/soong/.bootstrap/build.ninja.d -o
> out/soong/.bootstrap/build.ninja Android.bp
> internal error: could not open symlink hardware/qcom/sdm845/Android.bp;
> its target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm8150p/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm7250/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm8150/Android.bp;
> its target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
> internal error: could not open symlink hardware/qcom/sm7150/Android.bp;
> its target (gps/os_pickup.bp) cannot be opened
> ninja: build stopped: subcommand failed.
> 16:32:42 soong minibootstrap failed with: exit status 1
>
>  failed to build some targets (4 seconds) 
>
> --
> --
> 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/d1c3b2ed-8460-4704-b98c-c6b3085cead4n%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/CALQgHdk9Hkn6uDm4cQfZ9LHWLwO-Z3q5ERfLYSb4k6YE68VhLA%40mail.gmail.com.

[android-building] aosp for x86

2020-11-09 Thread Ovidio Pirvu 
Hello all,
as per the title I have built aosp 11 for the x86 platform but I'm stuck at 
how to compile the resulting built files in to a bootable iso. Any help 
would be apreciated.

Thank you

-- 
-- 
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/26c96580-e17a-41c2-8426-1653d6051ab1n%40googlegroups.com.

[android-building] android-9.0.0_r8 build error

2020-11-09 Thread Arthur Clark 
this is output message:


PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-42-generic-x86_64-Ubuntu-18.04.5-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PPR2.180905.006.A1
OUT_DIR=out

[1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja
FAILED: out/soong/.bootstrap/build.ninja 
out/soong/.minibootstrap/minibp -t -l out/.module_paths/Android.bp.list -b 
out/soong -n out -d out/soong/.bootstrap/build.ninja.d -o 
out/soong/.bootstrap/build.ninja Android.bp
internal error: could not open symlink hardware/qcom/sdm845/Android.bp; its 
target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
internal error: could not open symlink hardware/qcom/sm8150p/Android.bp; 
its target (gps/os_pickup.bp) cannot be opened
internal error: could not open symlink hardware/qcom/sm7250/Android.bp; its 
target (gps/os_pickup.bp) cannot be opened
internal error: could not open symlink hardware/qcom/sm8150/Android.bp; its 
target (data/ipacfg-mgr/os_pickup.bp) cannot be opened
internal error: could not open symlink hardware/qcom/sm7150/Android.bp; its 
target (gps/os_pickup.bp) cannot be opened
ninja: build stopped: subcommand failed.
16:32:42 soong minibootstrap failed with: exit status 1

 failed to build some targets (4 seconds) 

-- 
-- 
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/d1c3b2ed-8460-4704-b98c-c6b3085cead4n%40googlegroups.com.

[android-building] crDroid 7 (Android 11) Building Error

2020-11-09 Thread Spidey Goku 
spidey@Spidey:~/crDroid$ brunch lineage_z2_plus-userdebug Trying 
dependencies-only mode on a non-existing device tree? 
 PLATFORM_VERSION_CODENAME=REL 
PLATFORM_VERSION=11 CR_VERSION=7.0 TARGET_DEVICE=z2_plus 
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-5.4.0-52-generic-x86_64-Ubuntu-18.04.5-LTS 
HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 
HOST_BUILD_TYPE=release BUILD_ID=RP1A.201105.002 OUT_DIR=out 
PRODUCT_SOONG_NAMESPACES=vendor/zuk/z2_plus vendor/zuk/msm8996-common 
device/zuk/msm8996-common hardware/qcom-caf/msm8996 
vendor/qcom/opensource/data-ipa-cfg-mgr 
 06:41:31 
 06:41:31 You 
are building on a machine with 7.75GB of RAM 06:41:31 06:41:31 The minimum 
required amount of free memory is around 16GB, 06:41:31 and even with that, 
some configurations may not work. 06:41:31 06:41:31 If you run into 
segfaults or other errors, try reducing your 06:41:31 -j value. 06:41:31 
 
 PLATFORM_VERSION_CODENAME=REL 
PLATFORM_VERSION=11 CR_VERSION=7.0 TARGET_DEVICE=z2_plus 
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-5.4.0-52-generic-x86_64-Ubuntu-18.04.5-LTS 
HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 
HOST_BUILD_TYPE=release BUILD_ID=RP1A.201105.002 OUT_DIR=out 
PRODUCT_SOONG_NAMESPACES=vendor/zuk/z2_plus vendor/zuk/msm8996-common 
device/zuk/msm8996-common hardware/qcom-caf/msm8996 
vendor/qcom/opensource/data-ipa-cfg-mgr 
 
device/zuk/msm8996-common/BoardConfigCommon.mk was modified, 
regenerating... device/zuk/msm8996-common/BoardConfigCommon.mk was 
modified, regenerating... [ 13% 37/266] including 
device/zuk/msm8996-common/Android.mk ... 
device/zuk/msm8996-common/camera/QCamera2/stack/mm-camera-interface/Android.mk: 
warning: libmmcamera_interface: LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
[ 44% 119/266] including hardware/qcom-caf/msm8996/Android.mk ... 
hardware/qcom-caf/msm8996/audio/hal/Android.mk: warning: 
audio.primary.msm8996: LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
hardware/qcom-caf/msm8996/display/include/Android.mk:20: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/sdm/libs/utils/Android.mk:33: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/sdm/libs/core/Android.mk:71: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/sdm/libs/core/Android.mk:84: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/libcopybit/Android.mk:23: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/gpu_tonemapper/Android.mk:8: warning: 
BUILD_COPY_HEADERS has been deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers.
 
hardware/qcom-caf/msm8996/display/libdrmutils/Android.mk: warning: 
libdrmutils: LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
hardware/qcom-caf/msm8996/display/gralloc/../common.mk: warning: 
gralloc.msm8996: LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
hardware/qcom-caf/msm8996/media/mm-core/Android.mk: warning: libOmxCore: 
LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
hardware/qcom-caf/msm8996/media/libstagefrighthw/Android.mk: warning: 
libstagefrighthw: LOCAL_COPY_HEADERS is deprecated. See 
https://android.googlesource.com/platform/build/+/master/Changes.md#copy_headers
 
[ 70% 187/266] including system/sepolicy/Android.mk ...

[android-building] Re: AOSP repo sync command issue on Mac OS Catalina

2020-11-09 Thread Connor Tumbleson 
I'm just doing a regular master partial clone as well on Catalina and get 
that. My ubuntu machine has no issue syncing, so my guess is something in 
this new Catalina network stack isn't playing nice.

On Friday, August 28, 2020 at 2:36:26 PM UTC-4 vcamo...@gmail.com wrote:

> Based on the instruction, I tried 
>
> "repo init -u https://android.googlesource.com/platform/manifest -b 
> android-10.0.0_r40 --partial-clone "
>
> And then, "repo sync".
>
> However it failed many times as I re-try it many times, and the errors are:
> RPC failed; HTTP 499 curl 16 Error in the HTTP2 framing layer
> fatal: the remote end hung up unexpectedly
>
> RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
> fatal: the remote end hung up unexpectedly
>
> Does anyone know how we can make it?
>
> Thanks a lot!
>
>

-- 
-- 
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/2b87b591-2a61-4126-8d21-7ec52d41fe4dn%40googlegroups.com.