Build error for msm8916_64-userdebug target(Android M code),"make: *** [out/target/product/msm8916_64/system/bin/install-recovery.sh] Error 1" this error & build fails


#1

I have synced Android 6.0.1 source code properly by these commands,
repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.BR.1.2.6-04910-8x16.0.xml --repo-url=git://codeaurora.org/tools/repo.git
repo sync -j16

But,
while Building for msm8916_64-userdebug target I am facing build error.Following is the build error.I have referred links even though i facing same issue.

Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in
using prebuilt recovery.img from BOOTABLE_IMAGES…
using prebuilt boot.img from BOOTABLE_IMAGES…
Traceback (most recent call last):
File “./build/tools/releasetools/make_recovery_patch”, line 53, in
main(sys.argv[1:])
File “./build/tools/releasetools/make_recovery_patch”, line 49, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File “/data/android_TV/build/tools/releasetools/common.py”, line 1398, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File “/data/android_TV/build/tools/releasetools/common.py”, line 1089, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File “/data/android_TV/build/tools/releasetools/common.py”, line 83, in Run
return subprocess.Popen(args, **kwargs)
File “/usr/lib/python2.7/subprocess.py”, line 710, in init
errread, errwrite)
File “/usr/lib/python2.7/subprocess.py”, line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [out/target/product/msm8916_64/system/bin/install-recovery.sh] Error 1

make failed to build some targets (04:35:30 (hh:mm:ss))

Please Help


#2

Hi,

Commands used just for clone the CAF Manifest, along with it you need prebuilt floders to complete AOSP.

So, for Dragon Board 410c Qualcomm as posted Android M code in Qualcomm Developer Network.

please find the android M source from here
https://developer.qualcomm.com/download/db410c/android_board_support_package_vla.br_.1.2.7-01010-8x16.0-4.zip

After downloading the package please unzip it and run the .sh script file, it clone and compile the Andorid M for DB410c.

Thanks
Ramesh


#3

Hi Ramesh,

The same DB410c_build.sh script I executed. Even though I am facing this issue.I didn’t change anything in the script.I have executed complete script,only small portion of script sceenshot I attached


#4

Hi,

By default script should work, Because Qualcomm team will verify it then posted to QDN,
Can you please share error log snippet.

FYI
please make sure the Linux Android build set up pre-requests from here https://developer.qualcomm.com/download/db410c/linux-android-software-build-and-installation-guide.pdf

Thanks,
Ramesh


#5

Hi Ramesh,
I have tried building I am getting same errors.Here is log snippet.


#6

I can only really throw in a “works for me”.

I have a Ubuntu 14.04 container that I use to Android builds and DB410c_build.sh ran through cleanly for me (from start to finish, including the repo sync).

What version of GNU/Linux are you trying to run the build on?


#7

According to the code you’re missing either “bsdiff” or “imgdiff”, but I believe imgdiff comes with the releasetools so please install the prior on your system and try again.

Regards,
Bjorn


#8

I am also using Ubuntu 14.04 LTS and there were no fetch errors also.


#9

Hi @bamse

imgdiff should be built by the android build system (out/host/linux-x86/bin/imgdiff from source in bootable/recovery/applypatch/imgdiff.c).

@Mallamma: Do you have these files?

Daniel.


#10

yes, Now build is successful but when I flash the images for 2 to 3 secs, adb devices is detecting
root@mallamma:/home/mallamma/ubuntu_img# adb devices
List of devices attached
45920c8 device
after after some time as recovery device.
root@mallamma:/home/mallamma/ubuntu_img# adb devices
List of devices attached
45920c8 recovery


#11

I’m afraid you’ve lost me. Can you explain what you did to install the images, what you expected to happen and what actually happened?


#12

Hi Danielt,
I Executed following commands
$make clean
$source build/envsetup.sh
$lunch msm8916_64_userdebug
$make -j4 otatools
$make

These Commands I executed.Build successful, then I flashed images.


#13

What I mean is that I can’t work out what the question you are asking in your post about adb:

The three questions in my last mail (how you did it, what you expected, what you observed) are a common pattern to encourage (much) more detail to be supplied.

For example you’ve not commented about what instructions you are following to flash the images. Likewise it is not clear whether or not you get any HDMI or UART output (nor confirmed that you do get HDMI output using the pre-built Android images).


#14

I flashed pre-built android images, the HDMI output is proper and everything working fine.
When I build images from the generated source code, I am facing issues. The following are steps for building and flashing.
$make clean
$source build/envsetup.sh
$lunch msm8916_64-userdebug
$make -j4 otatools
$make
[make completed successfully]
Hold volume down and plug the power adapter
$fastboot devices
$fastboot flash boot boot.img
$fastboot flash userdata userdata.img
$fastboot flash cache cache.img
$fastboot flash recovery recovery.img
$fastboot flash persist persist.img
$fastboot flash system system.img
$fastboot reboot
Then I checked adb devices
$adb devices
List of devices attached
45920c8 recovery

HDMI OUTPUT When I use otatools command there is no build errors.
r1


If i didn’t use otatools command same build errors.
make: *** [out/target/product/msm8916_64/system/bin/install-recovery.sh] Error 1


#15

Thanks for the extra detail.

I’ve just confirmed that I am able to create working images, that boot and show the Launcher on HDMI, using just these bare commands (i.e. without an environment variables created inside the DB410c_build.sh script):

make clean
source build/envsetup.sh
lunch msm8916_64-userdebug
make

That you need to do something else does strongly suggest that either your source tree didn’t sync/patch properly, that there is some host tool missing that I have installed and you don’t or that there is something in your environment variables (.bashrc) that is causing the build to deviate from mine.

As to what we can do about that… I’m about to kick off a single threaded build (make -j 1 | tee stdout.log). It will take a long, long time but it will build files in a predictable order allowing us to diff log files. When its finished I’ll share stdout.log and you can compare it to the same command run on your system.

I’d also recommend you create a new user on your workstation, unzip the original Android .zip file from Qualcomm and run DB410c_build.sh from scratch. This ensures there is no contamination of the build by environment variables your normal user has lying around. If it doesn’t work clean up and try a single threaded build so we can compare.


#16

I have downloaded source code, there were no errors but patches from PATCH_8x16_410c_LA.BR.1.2.7-01010-8x16.0 directory were not applied to source code
but I didn’t apply any patches.
I have stared building the fresh source code with make -j1 |tee build-log.txt
Same issue i have facing.

what I Should change in .bashrc?

please share build logs so I will compare.


#17

Why not? The build script should do this automatically as soon as the code is downloaded. What was the output from the build script when it failed to patch the source code?

No idea I’m afraid. In my experience people can be very creative in the ways they can mess up their environments (and .bashrc customizations are just one way to do it). That’s why when different people with the same distro and following instructions in the same PDF get different results I recommend creating a new user.

It is something of a long shot to be honest but we need to narrow down differences and environment is one possibility.

I’m afraid date stamps on my logs don’t “feel” right (not sure which is which) so rather than guess I will regenerate. Unfortunately it should take a good eight hours to complete…


#18

Hi @Mallamma

So… I have a mix of good and bad news.

The first thing is that by building with make -j 1 I am able to reproduce your build problem! That means you can probably stop worrying about your environment variables and what packages you have installed on your machine, they are very unlikely to be related to the problem you are having.

I can also confirm that I can workaround the problem by performing a parallel build (make -j 10 on an octa-core build machine).

This strongly suggests that there is a bug in the build system. Specifically it is likely that there is a missing dependency so that the imgdiff tool ends up being run before is has been compiled (single process builds run in strict dependency order, whilst parallel builds can look ahead and build stuff that we don’t yet require but that we will in the future).

What value for -j are you using? (even on a single or dual core machine timeslicing might mean that high values for -j result in the same by-luck-not-judgement build that I enjoyed until yesterday).


#19

Cool! Thanks!

This command saved my day.
But I have no idea why :joy:.

My build log
Generating master DTB... completed
chmod a+r out/target/product/msm8916_64/dt.img
out/host/linux-x86/bin/mkbootimg  --kernel out/target/product/msm8916_64/kernel --ramdisk out/target/product/msm8916_64/ramdisk.img --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk androidboot.selinux=permissive" --base 0x80000000 --pagesize 2048  --output out/target/product/msm8916_64/boot.img
out/host/linux-x86/bin/boot_signer /boot out/target/product/msm8916_64/boot.img build/target/product/security/verity.pk8 build/target/product/security/verity.x509.pem out/target/product/msm8916_64/boot.img
size=$(for i in out/target/product/msm8916_64/boot.img; do stat --format "%s" "$i" | tr -d '\n'; echo +; done; echo 0); total=$(( $( echo "$size" ) )); printname=$(echo -n "out/target/product/msm8916_64/boot.img" | tr " " +); img_blocksize=135168; twoblocks=$((img_blocksize * 2)); onepct=$(((((34603008 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=$((twoblocks > onepct ? twoblocks : onepct)); maxsize=$((34603008 - reserve)); echo "$printname maxsize=$maxsize blocksize=$img_blocksize total=$total reserve=$reserve"; if [ "$total" -gt "$maxsize" ]; then echo "error: $printname too large ($total > [34603008 - $reserve])"; false; elif [ "$total" -gt $((maxsize - 32768)) ]; then echo "WARNING: $printname approaching size limit ($total now; limit $maxsize)"; fi 
out/target/product/msm8916_64/boot.img maxsize=34197504 blocksize=135168 total=17210664 reserve=405504
----- Making recovery image ------
mkdir -p out/target/product/msm8916_64/recovery
mkdir -p out/target/product/msm8916_64/recovery/root/etc out/target/product/msm8916_64/recovery/root/tmp
Copying baseline ramdisk...
rsync -a out/target/product/msm8916_64/root out/target/product/msm8916_64/recovery # "cp -Rf" fails to overwrite broken symlinks on Mac.
Modifying ramdisk contents...
rm -f out/target/product/msm8916_64/recovery/root/init*.rc
cp -f bootable/recovery/etc/init.rc out/target/product/msm8916_64/recovery/root/
rm -f out/target/product/msm8916_64/recovery/root/sepolicy
cp -f out/target/product/msm8916_64/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery out/target/product/msm8916_64/recovery/root/sepolicy
cp out/target/product/msm8916_64/root/init.recovery.*.rc out/target/product/msm8916_64/recovery/root/ || true # Ignore error when the src file doesn't exist.
cp: cannot stat ‘out/target/product/msm8916_64/root/init.recovery.*.rc’: No such file or directory
mkdir -p out/target/product/msm8916_64/recovery/root/res
rm -rf out/target/product/msm8916_64/recovery/root/res/*
cp -rf bootable/recovery/res-xhdpi/* out/target/product/msm8916_64/recovery/root/res
cp -f bootable/recovery/fonts/12x22.png out/target/product/msm8916_64/recovery/root/res/images/font.png
cp -f device/qcom/msm8916_64/recovery.fstab out/target/product/msm8916_64/recovery/root/etc/recovery.fstab
cp out/target/product/msm8916_64/obj/PACKAGING/ota_keys_intermediates/keys out/target/product/msm8916_64/recovery/root/res/keys
cat out/target/product/msm8916_64/root/default.prop out/target/product/msm8916_64/obj/ETC/system_build_prop_intermediates/build.prop > out/target/product/msm8916_64/recovery/root/default.prop
out/host/linux-x86/bin/mkbootfs -d out/target/product/msm8916_64/system out/target/product/msm8916_64/recovery/root | out/host/linux-x86/bin/minigzip > out/target/product/msm8916_64/ramdisk-recovery.img
out/host/linux-x86/bin/mkbootimg  --kernel out/target/product/msm8916_64/kernel  --ramdisk out/target/product/msm8916_64/ramdisk-recovery.img --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk androidboot.selinux=permissive" --base 0x80000000 --pagesize 2048  --output  out/target/product/msm8916_64/recovery.img --id > out/target/product/msm8916_64/recovery.id
out/host/linux-x86/bin/boot_signer /recovery  out/target/product/msm8916_64/recovery.img build/target/product/security/verity.pk8 build/target/product/security/verity.x509.pem  out/target/product/msm8916_64/recovery.img
size=$(for i in  out/target/product/msm8916_64/recovery.img; do stat --format "%s" "$i" | tr -d '\n'; echo +; done; echo 0); total=$(( $( echo "$size" ) )); printname=$(echo -n " out/target/product/msm8916_64/recovery.img" | tr " " +); img_blocksize=135168; twoblocks=$((img_blocksize * 2)); onepct=$(((((34603008 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=$((twoblocks > onepct ? twoblocks : onepct)); maxsize=$((34603008 - reserve)); echo "$printname maxsize=$maxsize blocksize=$img_blocksize total=$total reserve=$reserve"; if [ "$total" -gt "$maxsize" ]; then echo "error: $printname too large ($total > [34603008 - $reserve])"; false; elif [ "$total" -gt $((maxsize - 32768)) ]; then echo "WARNING: $printname approaching size limit ($total now; limit $maxsize)"; fi 
+out/target/product/msm8916_64/recovery.img maxsize=34197504 blocksize=135168 total=17980716 reserve=405504
----- Made recovery image: out/target/product/msm8916_64/recovery.img --------
Target build info: out/target/product/msm8916_64/system/build.prop
cat out/target/product/msm8916_64/obj/ETC/system_build_prop_intermediates/build.prop > out/target/product/msm8916_64/system/build.prop
echo ro.expect.recovery_id=`cat out/target/product/msm8916_64/recovery.id` >> out/target/product/msm8916_64/system/build.prop
mkisofs -o out/target/product/msm8916_64/system/etc/cdrom_install.iso  device/qcom/msm8916_64/cdrom_res
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
484 extents written (0 MB)
cp -f vendor/qcom/opensource/kernel-tests/bam_dmux_loopback/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/bam_dmux_loopback/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/bam_dmux_loopback O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/bus-timeout/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/bus-timeout/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/bus-timeout O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/coresight/profile/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/coresight/profile/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/coresight/profile O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/hrtimer/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/hrtimer/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/hrtimer O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ip_accelerator/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ip_accelerator/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ip_accelerator O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "ipa_sys_setup" [../vendor/qcom/opensource/kernel-tests/ip_accelerator/ipa_test_module.ko] undefined!
WARNING: "ipa_sys_teardown" [../vendor/qcom/opensource/kernel-tests/ip_accelerator/ipa_test_module.ko] undefined!
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ipc_logging/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ipc_logging/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ipc_logging O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ipi/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ipi/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ipi O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ldrex_strex/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ldrex_strex/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ldrex_strex O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/modsign/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/modsign/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/modsign O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ion/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ion/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ion O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/ocmem/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/ocmem/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/ocmem O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/watchdog/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/watchdog/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/watchdog O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/page-nom/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/page-nom/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/page-nom O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/wlan/prima/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/Kbuild
make -C kernel M=../vendor/qcom/opensource/wlan/prima O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules WLAN_ROOT=../vendor/qcom/opensource/wlan/prima MODNAME=wlan BOARD_PLATFORM=msm8916 CONFIG_PRONTO_WLAN=m
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
  LD [M]  ../vendor/qcom/opensource/wlan/prima/wlan.ko
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
mv -f out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/wlan.ko out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko
mkdir -p out/target/product/msm8916_64/obj/DLKM/pronto_wlan.ko_intermediates/
cp out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko.unstripped
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-strip --strip-debug out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko
cp out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko.stripped
Signing kernel module:  pronto_wlan.ko
target Prebuilt: pronto_wlan.ko (out/target/product/msm8916_64/obj/DLKM/pronto_wlan.ko_intermediates/pronto_wlan.ko)
out/host/linux-x86/bin/acp -fp out/target/product/msm8916_64/obj/vendor/qcom/opensource/wlan/prima/pronto_wlan.ko out/target/product/msm8916_64/obj/DLKM/pronto_wlan.ko_intermediates/pronto_wlan.ko
Install: out/target/product/msm8916_64/system/lib/modules/pronto/pronto_wlan.ko
out/host/linux-x86/bin/acp -fp out/target/product/msm8916_64/obj/DLKM/pronto_wlan.ko_intermediates/pronto_wlan.ko out/target/product/msm8916_64/system/lib/modules/pronto/pronto_wlan.ko
cp -f vendor/qcom/opensource/kernel-tests/spinlock/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/spinlock/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/spinlock O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/memory_prof/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/memory_prof/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/memory_prof O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
cp -f vendor/qcom/opensource/kernel-tests/abnormal_reset/Kbuild out/target/product/msm8916_64/obj/vendor/qcom/opensource/kernel-tests/abnormal_reset/Kbuild
make -C kernel M=../vendor/qcom/opensource/kernel-tests/abnormal_reset O=../out/target/product/msm8916_64/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- KCFLAGS=-mno-android modules 
make[1]: Entering directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/kernel'
build/tools/generate-notice-files.py  out/target/product/msm8916_64/obj/NOTICE.txt  out/target/product/msm8916_64/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" out/target/product/msm8916_64/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
out/host/linux-x86/bin/minigzip -9 < out/target/product/msm8916_64/obj/NOTICE.html > out/target/product/msm8916_64/obj/NOTICE.html.gz
out/host/linux-x86/bin/acp -fp out/target/product/msm8916_64/obj/NOTICE.html.gz out/target/product/msm8916_64/system/etc/NOTICE.html.gz
mkdir -p out/target/product/msm8916_64/system/etc/
find out/target/product/msm8916_64/recovery/root/res -type f | sort | zip -0qrj out/target/product/msm8916_64/system/etc/recovery-resource.dat -@
Installing recovery patch to system partition
mkdir -p out/target/product/msm8916_64/ota_temp
mkdir -p out/target/product/msm8916_64/ota_temp/BOOT
mkdir -p out/target/product/msm8916_64/ota_temp/RECOVERY
mkdir -p out/target/product/msm8916_64/ota_temp/BOOTABLE_IMAGES
mkdir -p out/target/product/msm8916_64/ota_temp/SYSTEM
mkdir -p out/target/product/msm8916_64/ota_temp/SYSTEM/bin
mkdir -p out/target/product/msm8916_64/ota_temp/SYSTEM/etc
mkdir -p out/target/product/msm8916_64/ota_temp/META
if [ -d "out/target/product/msm8916_64/recovery/root" -a "$(ls -A  out/target/product/msm8916_64/recovery/root)" ]; then mkdir -p out/target/product/msm8916_64/ota_temp/RECOVERY/RAMDISK && out/host/linux-x86/bin/acp -rd out/target/product/msm8916_64/recovery/root/* out/target/product/msm8916_64/ota_temp/RECOVERY/RAMDISK; fi
if [ -d "out/target/product/msm8916_64/root" -a "$(ls -A  out/target/product/msm8916_64/root)" ]; then mkdir -p out/target/product/msm8916_64/ota_temp/BOOT/RAMDISK && out/host/linux-x86/bin/acp -rd out/target/product/msm8916_64/root/* out/target/product/msm8916_64/ota_temp/BOOT/RAMDISK; fi
if [ -d "out/target/product/msm8916_64/system/etc" -a "$(ls -A  out/target/product/msm8916_64/system/etc)" ]; then mkdir -p out/target/product/msm8916_64/ota_temp/SYSTEM/etc && out/host/linux-x86/bin/acp -rd out/target/product/msm8916_64/system/etc/* out/target/product/msm8916_64/ota_temp/SYSTEM/etc; fi
echo "fs_type=ext4" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "system_size=1288491008" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "userdata_size=5368709120" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "cache_fs_type=ext4" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "cache_size=268435456" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "extfs_sparse_flag=-s" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "selinux_fc=out/target/product/msm8916_64/root/file_contexts" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "boot_signer=true" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "verity=true" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "verity_key=build/target/product/security/verity" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "verity_signer_cmd=out/host/linux-x86/bin/verity_signer" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
echo "system_verity_block_device=/dev/block/bootdevice/by-name/system" >>  out/target/product/msm8916_64/ota_temp/META/misc_info.txt
cp -r out/target/product/msm8916_64/boot.img out/target/product/msm8916_64/ota_temp/BOOTABLE_IMAGES/
cp -r out/target/product/msm8916_64/recovery.img out/target/product/msm8916_64/ota_temp/BOOTABLE_IMAGES/
./build/tools/releasetools/make_recovery_patch out/target/product/msm8916_64/ota_temp out/target/product/msm8916_64/ota_temp
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
Traceback (most recent call last):
  File "./build/tools/releasetools/make_recovery_patch", line 53, in <module>
    main(sys.argv[1:])
  File "./build/tools/releasetools/make_recovery_patch", line 49, in main
    common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
  File "/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/build/tools/releasetools/common.py", line 1398, in MakeRecoveryPatch
    _, _, patch = d.ComputePatch()
  File "/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/build/tools/releasetools/common.py", line 1089, in ComputePatch
    p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/home/vutuda/embedded/dragonboard410c/bsp/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8x16.0_6.0.1_Marsh_Mallo_P2/build/tools/releasetools/common.py", line 83, in Run
    return subprocess.Popen(args, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [out/target/product/msm8916_64/system/bin/install-recovery.sh] Error 1

#### make failed to build some targets (08:37 (mm:ss)) ####