[RESOLVED]Problem while building CM12 based ROM - Asus Transformer TF700
Hello,
Today i tried to "do" a CM12 based ROM but i have a problem during the build.
i tried a hundred times but everytime, it fails...
Code:
/home/maxime/test/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/bin/../lib/gcc/x86_64-linux/4.6/../../../../x86_64-linux/bin/ld: error: /home/maxime/test/out/host/linux-x86/obj32/EXECUTABLES/rsg-generator_support_intermediates/rsg_generator.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/bin/../lib/gcc/x86_64-linux/4.6/../../../../x86_64-linux/bin/ld: error: /home/maxime/test/out/host/linux-x86/obj32/EXECUTABLES/rsg-generator_support_intermediates/spec.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/bin/../sysroot/usr/lib/../lib32/Scrt1.o(.text+0x28): error: undefined reference to 'main'
target thumb C++: libjni_pacprocessor <= frameworks/base/packages/services/PacProcessor/jni/com_android_pacprocessor_PacNative.cpp
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/././../home../maxime/test/..prebuilts/gcc//linux-armx86/arm-linux/arm--linux-androideabiandroideabi-4.8//bin/.bin/./libld/gcc/:arm- errorlinux-: /androideabi/home/4.8/maxime/..test/out/./target.//product../tf700t/./obj./arm/SHARED_LIBRARIES-linux/libjni_eglfence_intermediates-androideabi/jni_egl_fence.o/bin: /ld:file is error empty:
/home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_tinyplanet_intermediates/tinyplanet.o: file is empty
collect2: ld returned 1 exit status
target SharedLib: libjni_filtershow_filters (/home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/LINKED/libjni_filtershow_filters.so)
make: *** [/home/maxime/test/out/host/linux-x86/obj32/EXECUTABLES/rsg-generator_support_intermediates/rsg-generator_support] Erreur 1
make: *** Attente des tâches non terminées....
target thumb C++: libpac <= external/chromium-libpac/src/proxy_resolver_v8.cc
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/tinyplanet.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/kmeans.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/gradient.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/saturated.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/exposure.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/edge.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/contrast.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/hue.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/shadows.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/highlight.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/hsv.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/vibrance.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/geometry.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/negative.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/redEyeMath.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/fx.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/wbalance.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/redeye.o: file is empty
/home/maxime/test/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/filters/bwfilter.o: file is empty
collect2: error: ld returned 1 exit status
collect2: error: ld returned 1 exit status
make: *** [/home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_eglfence_intermediates/LINKED/libjni_eglfence.so] Erreur 1
make: *** [/home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_filtershow_filters_intermediates/LINKED/libjni_filtershow_filters.so] Erreur 1
collect2: error: ld returned 1 exit status
make: *** [/home/maxime/test/out/target/product/tf700t/obj/SHARED_LIBRARIES/libjni_tinyplanet_intermediates/LINKED/libjni_tinyplanet.so] Erreur 1
frameworks/base/packages/services/PacProcessor/jni/jni_init.cpp:28:17: warning: unused parameter 'reserved' [-Wunused-parameter]
extern "C" jint JNI_OnLoad(JavaVM* vm, void* reserved) {
^
frameworks/base/packages/services/PacProcessor/jni/com_android_pacprocessor_PacNative.cpp:63:17: warning: unused parameter 'env' [-Wunused-parameter]
static jboolean com_android_pacprocessor_PacNative_createV8ParserNativeLocked(JNIEnv* env,
^
frameworks/base/packages/services/PacProcessor/jni/com_android_pacprocessor_PacNative.cpp:75:17: warning: unused parameter 'env' [-Wunused-parameter]
static jboolean com_android_pacprocessor_PacNative_destroyV8ParserNativeLocked(JNIEnv* env,
^
make: *** wait: Aucun processus enfant. Arrêt.
#### make failed to build some targets (02:05 (mm:ss)) ####
Thank you
maxou2600 said:
Code:
/home/maxime/test/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/bin/../lib/gcc/x86_64-linux/4.6/../../../../x86_64-linux/bin/ld: error: /home/maxime/test/out/host/linux-x86/obj32/EXECUTABLES/rsg-generator_support_intermediates/rsg_generator.o: file is empty
...[/QUOTE]
Weird error. Have you tried "make clean" and rebuilding?
Click to expand...
Click to collapse
Thank you
Yep' i tried it unsuccessfully...
i Think that a lot of files were corrupted (Bad ADSL connection, with lot of FEC, HEC and CRC...)
I removed the "test" folder and resync all the files during the night (about 15-20GB)
Now after half an hour i have that error
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:27 (mm:ss)) ####
in folder ~/test/out/target/product/tf700t i found a file called "ramdisk-recovery.img", i renamed it to "ramdisk-recovery.cpio" but i think it was not the same file because now i have this error.
Code:
mkdir -p /home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/maxime/test/out/host/linux-x86/bin:$PATH /home/maxime/test/out/host/linux-x86/bin/imgdiff /home/maxime/test/out/target/product/tf700t/boot.img /home/maxime/test/out/target/product/tf700t/recovery.img /home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 4253810
chunk 1: type 2 start 4253810 len 1161984
chunk 2: type 0 start 4927508 len 84
target chunks:
chunk 0: type 0 start 0 len 7227496
make: *** [/home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Erreur 1
make: *** Attente des tâches non terminées....
So, i "make clean" and "brunch" again. I tell you if the first error (No such File or directory) re-comes (no-reason )
yep' same as this morning :
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:30 (mm:ss)) ####
EDIT : At the begin of the build i got some errors (I Don't know if it's a problem, i think it's not otherwise build stop like (Ramdisk-recovery.cpio error...) :
Code:
No private recovery resources for TARGET_DEVICE tf700t
"ebtables is disabled on this build"
After some research i think that the "ramdisk_recovery" isn't "created" during the build.
I changed the Recovery.mk in /device/asus/tf700t
The original
Code:
TF_BLOBIFIER := $(HOST_OUT_EXECUTABLES)/blobpack_tfp
LZMA_BIN := /usr/bin/lzma
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
@echo ----- Compressing recovery ramdisk with lzma ------
rm -f $(recovery_uncompressed_ramdisk).lzma
$(LZMA_BIN) $(recovery_uncompressed_ramdisk)
$(hide) cp $(recovery_uncompressed_ramdisk).lzma $(recovery_ramdisk)
@echo ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
@echo ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(TF_BLOBIFIER)
$(call pretty,"Target boot image: [email protected]")
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] LNX [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)
give me
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:30 (mm:ss)) ####
and the modified
Code:
TF_BLOBIFIER := $(HOST_OUT_EXECUTABLES)/blobpack_tfp
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
@echo ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
@echo ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(TF_BLOBIFIER)
$(call pretty,"Target boot image: [email protected]")
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] LNX [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)
give me
Code:
----- Making recovery image ------
/home/maxime/test/out/host/linux-x86/bin/mkbootimg --kernel /home/maxime/test/out/target/product/tf700t/kernel --ramdisk /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.img --cmdline "androidboot.selinux=enforcing" --base 0x10000000 --output /home/maxime/test/out/target/product/tf700t/recovery.img.orig
/home/maxime/test/out/host/linux-x86/bin/blobpack_tfp /home/maxime/test/out/target/product/tf700t/recovery.img SOS /home/maxime/test/out/target/product/tf700t/recovery.img.orig
Found 1 partitions as commandline arguments
Partname: SOS Filename: /home/maxime/test/out/target/product/tf700t/recovery.img.orig
Size: 60
1 partitions starting at offset 0x3C
Offset: 76
----- Made recovery image -------- /home/maxime/test/out/target/product/tf700t/recovery.img
/home/maxime/test/out/target/product/tf700t/recovery.img maxsize=8562048 blocksize=4224 total=9359464 reserve=88704
error: /home/maxime/test/out/target/product/tf700t/recovery.img too large (9359464 > [8650752 - 88704])
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Destruction du fichier « /home/maxime/test/out/target/product/tf700t/recovery.img »
#### make failed to build some targets (01:25 (mm:ss)) ####
Ideas ?
maxou2600 said:
Thank you
Yep' i tried it unsuccessfully...
i Think that a lot of files were corrupted (Bad ADSL connection, with lot of FEC, HEC and CRC...)
I removed the "test" folder and resync all the files during the night (about 15-20GB)
Now after half an hour i have that error
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:27 (mm:ss)) ####
in folder ~/test/out/target/product/tf700t i found a file called "ramdisk-recovery.img", i renamed it to "ramdisk-recovery.cpio" but i think it was not the same file because now i have this error.
Code:
mkdir -p /home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/maxime/test/out/host/linux-x86/bin:$PATH /home/maxime/test/out/host/linux-x86/bin/imgdiff /home/maxime/test/out/target/product/tf700t/boot.img /home/maxime/test/out/target/product/tf700t/recovery.img /home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 4253810
chunk 1: type 2 start 4253810 len 1161984
chunk 2: type 0 start 4927508 len 84
target chunks:
chunk 0: type 0 start 0 len 7227496
make: *** [/home/maxime/test/out/target/product/tf700t/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Erreur 1
make: *** Attente des tâches non terminées....
So, i "make clean" and "brunch" again. I tell you if the first error (No such File or directory) re-comes (no-reason )
yep' same as this morning :
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:30 (mm:ss)) ####
EDIT : At the begin of the build i got some errors (I Don't know if it's a problem, i think it's not otherwise build stop like (Ramdisk-recovery.cpio error...) :
Code:
No private recovery resources for TARGET_DEVICE tf700t
"ebtables is disabled on this build"
After some research i think that the "ramdisk_recovery" isn't "created" during the build.
I changed the Recovery.mk in /device/asus/tf700t
The original
Code:
TF_BLOBIFIER := $(HOST_OUT_EXECUTABLES)/blobpack_tfp
LZMA_BIN := /usr/bin/lzma
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
@echo ----- Compressing recovery ramdisk with lzma ------
rm -f $(recovery_uncompressed_ramdisk).lzma
$(LZMA_BIN) $(recovery_uncompressed_ramdisk)
$(hide) cp $(recovery_uncompressed_ramdisk).lzma $(recovery_ramdisk)
@echo ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
@echo ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(TF_BLOBIFIER)
$(call pretty,"Target boot image: $@")
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] LNX [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)
give me
Code:
/usr/bin/lzma : /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.cpio: Aucun fichier ou dossier de ce type
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Attente des tâches non terminées....
####make failed to build some targets (30:30 (mm:ss)) ####
and the modified
Code:
TF_BLOBIFIER := $(HOST_OUT_EXECUTABLES)/blobpack_tfp
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
@echo ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
@echo ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(TF_BLOBIFIER)
$(call pretty,"Target boot image: [email protected]")
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] LNX [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)
give me
Code:
----- Making recovery image ------
/home/maxime/test/out/host/linux-x86/bin/mkbootimg --kernel /home/maxime/test/out/target/product/tf700t/kernel --ramdisk /home/maxime/test/out/target/product/tf700t/ramdisk-recovery.img --cmdline "androidboot.selinux=enforcing" --base 0x10000000 --output /home/maxime/test/out/target/product/tf700t/recovery.img.orig
/home/maxime/test/out/host/linux-x86/bin/blobpack_tfp /home/maxime/test/out/target/product/tf700t/recovery.img SOS /home/maxime/test/out/target/product/tf700t/recovery.img.orig
Found 1 partitions as commandline arguments
Partname: SOS Filename: /home/maxime/test/out/target/product/tf700t/recovery.img.orig
Size: 60
1 partitions starting at offset 0x3C
Offset: 76
----- Made recovery image -------- /home/maxime/test/out/target/product/tf700t/recovery.img
/home/maxime/test/out/target/product/tf700t/recovery.img maxsize=8562048 blocksize=4224 total=9359464 reserve=88704
error: /home/maxime/test/out/target/product/tf700t/recovery.img too large (9359464 > [8650752 - 88704])
make: *** [/home/maxime/test/out/target/product/tf700t/recovery.img] Erreur 1
make: *** Destruction du fichier « /home/maxime/test/out/target/product/tf700t/recovery.img »
#### make failed to build some targets (01:25 (mm:ss)) ####
Ideas ?
Click to expand...
Click to collapse
Yes, I see exactly what is going on here .....
You need to install lzma on your host PC .....
So in /usr/bin/ you need to find a file called 'lzma'
Removing this from the recovery.mk ...
Code:
LZMA_BIN := /usr/bin/lzma
Has made the recovery to large to fix in the space provided by the device''s recovery partition ......
Code:
error: /home/maxime/test/out/target/product/tf700t/recovery.img too large (9359464 > [8650752 - 88704])
Thx Josh
Hello, I found the solution (thanks to _that in #TWRP IRC )
lzma was in usr/bin, no problem
the problem was that the ramdisk_recovery.cpio file wasn't found, the solution was to edit some lines (in red)
Code:
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_[COLOR="Red"]uncompressed_[/COLOR]ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
[user=279333]@ECHO[/user] ----- Compressing recovery ramdisk with lzma ------
rm -f $(recovery_uncompressed_ramdisk).lzma
$(LZMA_BIN) $(recovery_uncompressed_ramdisk)
$(hide) cp $(recovery_uncompressed_ramdisk).lzma $(recovery_[COLOR="Red"]uncompressed_[/COLOR]ramdisk)
[user=279333]@ECHO[/user] ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
[user=279333]@ECHO[/user] ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
After that, just needed to erase .ccache folder and make clean. And then recovery.img compiled successfully.
(sorry for bad english).
I will edit the title because it's resolved
please help
maxou2600 said:
Hello, I found the solution (thanks to _that in #TWRP IRC )
lzma was in usr/bin, no problem
the problem was that the ramdisk_recovery.cpio file wasn't found, the solution was to edit some lines (in red)
Code:
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) \
$(recovery_[COLOR="Red"]uncompressed_[/COLOR]ramdisk) \
$(TF_BLOBIFIER) \
$(recovery_kernel)
[user=279333]@ECHO[/user] ----- Compressing recovery ramdisk with lzma ------
rm -f $(recovery_uncompressed_ramdisk).lzma
$(LZMA_BIN) $(recovery_uncompressed_ramdisk)
$(hide) cp $(recovery_uncompressed_ramdisk).lzma $(recovery_[COLOR="Red"]uncompressed_[/COLOR]ramdisk)
[user=279333]@ECHO[/user] ----- Making recovery image ------
$(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) --output [email protected]
$(TF_BLOBIFIER) [email protected] SOS [email protected]
[user=279333]@ECHO[/user] ----- Made recovery image -------- [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
After that, just needed to erase .ccache folder and make clean. And then recovery.img compiled successfully.
(sorry for bad english).
I will edit the title because it's resolved
Click to expand...
Click to collapse
i also met the problem that boot.img too large when i compile recovery.img. how do you solve it. sorry for my ban english
Hello, I erased ccache folders and i make clean. After that, all was working fine
i fixed it.but also thank you
Related
[HELP] Android Kernel Building Errors. permission denied :(
Hi every body, i'm now building android kernel for SKY-VEGA-S5 phone ( IM-A840S). I followed these steps on the homepage of SKY . They're : 1. How to build Kernel source of UI18760_kernel a.First, Get Toolchain from android git server and etc ¡Š GCC correct version is arm-eabi-4.4.3 b.modify Makefile edit "CROSS_COMPILE" to toolchain path ( You downloaded ) ex) CROSS_COMPILE=$(You Download directory)/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- c.make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm msm8960_ef44s_tp20_defconfig d.make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm 2. Kernel Image Location is arch/arm/boot/zImage Module Image Location is drivers/*/*.ko 3. How to Clean Kernel object files a.make ARCH=arm clean ______________________________________________________________________________________ I downloaded the kernel package and extract to the /home folder. And toolchain ..... /prebuilt folder is also extracted to the /home folder. I modified Makefile. CROSS_COMPILE ?=$/home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- Then I step by step followed the guide. But i got many error... ( I think the PATH was wrong, but I dont know how to correctly edit it ==' ). Here they are : __________________________________________________________________________________________ [email protected]:~/kernel$ make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm "======================LINUX INCLUDE===========================================================" -I/home/vip7009pro/kernel/arch/arm/include -Iarch/arm/include/generated -Iinclude -include include/generated/autoconf.h "==============================================================================================" "KERNEL ======================================================================================" -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -DT_EF44S -I ./include/pantech -include ./include/pantech/CUST_PANTECH.h -DFIRM_VER=\"S0215141\" -DSYS_MODEL_NAME=\"EF44S\" -DPANTECH_MODEL_NAME=\"IM-A840S\" -DFS_USER_DATA_VER=37 -DPANTECH_STORAGE_INTERNAL_EMUL -DFEATURE_AARM_RELEASE_MODE -D__KERNELBUILD__ "==============================================================================================" CHK include/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CC kernel/bounds.s /home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc -Wp,-MD,kernel/.bounds.s.d -nostdinc -isystem /home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc -print-file-name=include [Errno 13] Permission denied -I/home/vip7009pro/kernel/arch/arm/include -Iarch/arm/include/generated -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -mlittle-endian -Iarch/arm/mach-msm/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -DT_EF44S -I ./include/pantech -include ./include/pantech/CUST_PANTECH.h -DFIRM_VER="S0215141" -DSYS_MODEL_NAME="EF44S" -DPANTECH_MODEL_NAME="IM-A840S" -DFS_USER_DATA_VER=37 -DPANTECH_STORAGE_INTERNAL_EMUL -DFEATURE_AARM_RELEASE_MODE -D__KERNELBUILD__ -O2 -fstack-protector -mabi=aapcs-linux -mno-thumb-interwork -funwind-tables -D__LINUX_ARM_ARCH__=7 -march=armv5t -Wa,-march=armv7-a -msoft-float -Uarm -fomit-frame-pointer -g -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(bounds) -DKBUILD_MODNAME=KBUILD_STR(bounds) -fverbose-asm -S -o kernel/bounds.s kernel/bounds.c [Errno 13] Permission denied make[1]: *** [kernel/bounds.s] Error 13 make: *** [prepare0] Error 2 [email protected]:~/kernel$ ____________________________________________________________________________________________________________ Can any one tell me what do these errors mean and how to fix them .. I'm looking forward to receiving answers from y0u all, soon .. Thanks
[HELP] Android Kernel Building Error. Permission denied :(
Hi every body, i'm now building android kernel for SKY-VEGA-S5 phone ( IM-A840S). I followed these steps on the homepage of SKY . They're : 1. How to build Kernel source of UI18760_kernel a.First, Get Toolchain from android git server and etc ¡Š GCC correct version is arm-eabi-4.4.3 b.modify Makefile edit "CROSS_COMPILE" to toolchain path ( You downloaded ) ex) CROSS_COMPILE=$(You Download directory)/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- c.make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm msm8960_ef44s_tp20_defconfig d.make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm 2. Kernel Image Location is arch/arm/boot/zImage Module Image Location is drivers/*/*.ko 3. How to Clean Kernel object files a.make ARCH=arm clean __________________________________________________ ____________________________________ I downloaded the kernel package and extract to the /home folder. And toolchain ..... /prebuilt folder is also extracted to the /home folder. I modified Makefile. CROSS_COMPILE ?=$/home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- Then I step by step followed the guide. But i got many error... ( I think the PATH was wrong, but I dont know how to correctly edit it ==' ). Here they are : __________________________________________________ ________________________________________ [email protected]:~/kernel$ make CONFIG_DEBUG_SECTION_MISMATCH=y ARCH=arm "======================LINUX INCLUDE=========================================== ================" -I/home/vip7009pro/kernel/arch/arm/include -Iarch/arm/include/generated -Iinclude -include include/generated/autoconf.h "================================================= =============================================" "KERNEL ================================================== ====================================" -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -DT_EF44S -I ./include/pantech -include ./include/pantech/CUST_PANTECH.h -DFIRM_VER=\"S0215141\" -DSYS_MODEL_NAME=\"EF44S\" -DPANTECH_MODEL_NAME=\"IM-A840S\" -DFS_USER_DATA_VER=37 -DPANTECH_STORAGE_INTERNAL_EMUL -DFEATURE_AARM_RELEASE_MODE -D__KERNELBUILD__ "================================================= =============================================" CHK include/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CC kernel/bounds.s /home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc -Wp,-MD,kernel/.bounds.s.d -nostdinc -isystem /home/vip7009pro/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc -print-file-name=include [Errno 13] Permission denied -I/home/vip7009pro/kernel/arch/arm/include -Iarch/arm/include/generated -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -mlittle-endian -Iarch/arm/mach-msm/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -DT_EF44S -I ./include/pantech -include ./include/pantech/CUST_PANTECH.h -DFIRM_VER="S0215141" -DSYS_MODEL_NAME="EF44S" -DPANTECH_MODEL_NAME="IM-A840S" -DFS_USER_DATA_VER=37 -DPANTECH_STORAGE_INTERNAL_EMUL -DFEATURE_AARM_RELEASE_MODE -D__KERNELBUILD__ -O2 -fstack-protector -mabi=aapcs-linux -mno-thumb-interwork -funwind-tables -D__LINUX_ARM_ARCH__=7 -march=armv5t -Wa,-march=armv7-a -msoft-float -Uarm -fomit-frame-pointer -g -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(bounds) -DKBUILD_MODNAME=KBUILD_STR(bounds) -fverbose-asm -S -o kernel/bounds.s kernel/bounds.c [Errno 13] Permission denied make[1]: *** [kernel/bounds.s] Error 13 make: *** [prepare0] Error 2 [email protected]:~/kernel$
dtbtool error (read i have some other questions too)
Hi there, ive almost posted atleast 5 times for errors and im really thankfull for all the help i got. im building pac-5.1 from source from my phone. my phones manufacturer (lenovo) did not release the complete source so im using the kernel of surnia (moto e 2015 4g) which also has the same kernel. my mkboot.img looks like this - Code: # Use prebuilt dt.img INSTALLED_DTIMAGE_TARGET := $(PRODUCT_OUT)/dt.img $(INSTALLED_DTIMAGE_TARGET): @echo -e ${CL_CYN}"Start DT image: [email protected]"${CL_RST} $(call append-dtb) $(call pretty,"Target dt image: $(INSTALLED_DTIMAGE_TARGET)") @echo -e ${CL_CYN}"Made DT image: [email protected]"${CL_RST} ## Overload bootimg generation: Same as the original, + --dt arg $(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(INSTALLED_DTIMAGE_TARGET) $(call pretty,"Target boot image: [email protected]") $(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected] $(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw) @echo -e ${CL_CYN}"Made boot image: [email protected]"${CL_RST} ## Overload recoveryimg generation: Same as the original, + --dt arg $(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) $(INSTALLED_DTIMAGE_TARGET) \ $(recovery_ramdisk) \ $(recovery_kernel) @echo -e ${CL_CYN}"----- Making recovery image ------"${CL_RST} $(hide) $(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected] $(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw) @echo -e ${CL_CYN}"Made recovery image: [email protected]"${CL_RST} and moto e's like this - Code: LOCAL_PATH := $(call my-dir) ## Build and run dtbtool [COLOR="Red"]DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbToolCM$(HOST_EXECUTABLE_SUFFIX)[/COLOR] INSTALLED_DTIMAGE_TARGET := $(PRODUCT_OUT)/dt.img $(INSTALLED_DTIMAGE_TARGET): $(DTBTOOL) $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr $(INSTALLED_KERNEL_TARGET) $(call pretty,"Target dt image: $(INSTALLED_DTIMAGE_TARGET)") $(hide) $(DTBTOOL) -2 -o $(INSTALLED_DTIMAGE_TARGET) -s $(BOARD_KERNEL_PAGESIZE) -p $(KERNEL_OUT)/scripts/dtc/ $(KERNEL_OUT)/arch/arm/boot/dts/ @echo -e ${CL_CYN}"Made DT image: [email protected]"${CL_RST} ## Overload bootimg generation: Same as the original, + --dt arg $(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(INSTALLED_DTIMAGE_TARGET) $(call pretty,"Target boot image: [email protected]") $(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected] $(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw) @echo -e ${CL_CYN}"Made boot image: [email protected]"${CL_RST} ## Overload recoveryimg generation: Same as the original, + --dt arg $(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) $(INSTALLED_DTIMAGE_TARGET) \ $(recovery_ramdisk) \ $(recovery_kernel) @echo -e ${CL_CYN}"----- Making recovery image ------"${CL_RST} $(hide) $(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected] $(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw) @echo -e ${CL_CYN}"Made recovery image: [email protected]"${CL_RST} i had to remove the highlited part in my mkboot.img because of this error Code: make: *** No rule to make target '/ home/bassface/PAC/out/host/linux-x86/bin/dtbToolCM' necessary '/ home/bassface/PAC/out/target/product /a6000/dt.img '. the rom succesfully compiles for 4+hours then stops saying it could not find dt.img in product/a6000 if i remove the Code: DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbToolCM$(HOST_EXECUTABLE_SUFFIX line. i just deleted the entire out ditrectory and im recompiling i placed the dt.img in now. but i want to know whats causing this error. why dont i have the dtbtool? is it supposed to be downloaded seperately.? evem if the rom builds succesfully after copying it and pasting in the out directory. what am i supposed to do for it to copy automatically in the future, if someone else wants to make something using my source? thankyou
Did you solve this? I'm struggling with this too... I know the dtbtool is in my repo... Thanks in advance, Yordi
I know this is quite old, but for people who have run into this problem like me, try adding this to your repo manifest. Adapt it according to the ROM you are building. <project path="system/tools/dtbtool" name="android_system_tools_dtbtool" remote="lineage" />
[Completed] cyanogenmod 12.1 build error(s) for hydro XTRM c6522n
As the title suggests I'm porting cyanogenmod to my old phone so when I root my hydro wave c6740n...I'll have the source & knowledge to do the same with the hydro wave as well, but back to my problem. I keep getting this error when ever i try to build the recovery. build/core/tasks/kernel.mk:290: warning: overriding recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/kernel' build/core/Makefile:46: warning: ignoring old recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/kernel' Target boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img maxsize=3514368 blocksize=135168 total=6680576 reserve=270336 error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img too large (6680576 > [3784704 - 270336]) build/core/Makefile:570: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img' failed make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img] Error 1 make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img' #### make failed to build some targets (02:55 (mm:ss)) #### it keeps stating its too large & i'm just stuck at this point.. also im trying to build recovery NOT the boot.img which I don't why it states boot.img instead of recovery. BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000 BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000 BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000 BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000 BOARD_FLASH_BLOCK_SIZE := 131072 aslo I am having trouble with the board config as well BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 no_console_suspend=1 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=312M BOARD_KERNEL_BASE := 0x BOARD_KERNEL_PAGESIZE := 2048 I don't know what the kernel base would be in the mess below... Kernel size 5820152 Kernel address 0x80208000 Ramdisk size 336324 Ramdisk address 0x82200000 Secondary size 0 Secondary address 0x81100000 Kernel tags address 0x80200100 Flash page size 2048 if you need more info to help just ask...I'm truly new to all this.
update-still not working, but... Target boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img maxsize=10040448 blocksize=135168 total=6676480 reserve=270336 Made boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img target StaticExecutable: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery) target Symbolic: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/symbols/system/bin/recovery) target Strip: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/obj/EXECUTABLES/recovery_intermediates/recovery) ----- Making recovery image ------ Copying baseline ramdisk... Modifying ramdisk contents... cp: cannot stat ‘/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/root/init.recovery.*.rc’: No such file or directory build/core/Makefile:944: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img' failed make: [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img] Error 1 (ignored) /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img maxsize=8177664 blocksize=135168 total=9250816 reserve=270336 error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img too large (9250816 > [8448000 - 270336]) build/core/Makefile:978: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' failed make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img] Error 1 make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' #### make failed to build some targets (11:50 (mm:ss)) #### build error! I tried many things now, but I can't seem to get the recovery maxsize right during build... im going to change the recovery size from 8000000 to 8177664
update 2-not working ----- Making recovery image ------ Copying baseline ramdisk... Modifying ramdisk contents... cp: cannot stat ‘/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/root/init.recovery.*.rc’: No such file or directory build/core/Makefile:944: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img' failed make: [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img] Error 1 (ignored) /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img maxsize=8162880 blocksize=135168 total=9250816 reserve=270336 error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img too large (9250816 > [8433216 - 270336]) build/core/Makefile:978: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' failed make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img] Error 1 make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' #### make failed to build some targets (10:29 (mm:ss)) #### I'm honestly stuck trying to build the recovery
almost working It's still saying that it's too large & i finally noticed i been missing a file called init.recovery.*.rc I gotten boardconfig.mk all set up and correct BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 no_console_suspend=1 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=312M BOARD_KERNEL_BASE := 0x80200000 BOARD_KERNEL_PAGESIZE := 2048 # fix this up by examining /proc/mtd on a running device BOARD_BOOTIMAGE_PARTITION_SIZE := 10485760 BOARD_RECOVERYIMAGE_PARTITION_SIZE := 8388608 BOARD_SYSTEMIMAGE_PARTITION_SIZE := 674234368 BOARD_USERDATAIMAGE_PARTITION_SIZE := 1073741824 BOARD_FLASH_BLOCK_SIZE := 131072 recovery.fstab # mount point fstype device [device2] /boot mtd /dev/block/mmcblk0p7 /cache yaffs2 /dev/block/mmcblk0p15 /data yaffs2 /dev/block/mmcblk0p13 /misc mtd /dev/block/mmcblk0p17 /recovery mtd /dev/block/mmcblk0p18 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 /system yaffs2 /dev/block/mmcblk0p12 /sd-ext ext4 /dev/block/mmcblk0p2 do I need to add more? such as ...0p1 to ..0p37 what else do I need to do?
I give up on cyanogenmod recovery BUT, I found a perfect substitute for it...PhilZ recovery.img for hydro xtrm c6522 varients I tested it & works like a charm, but the only downside is that you have to constantly connect your PC and boot(NOT FLASH) into PhilZ recovery. so I made all steps easier by creating script(s) & provide the PhilZ recovery & stock recovery. 1. please open a terminal within the folder with all the files 2. you can either run & read the help.sh or just run setup.sh (basically the same info, but setup.sh starts the process) to run the scripts please type "./setup.sh" without "" the following info in the script will tell you what to do from then on. NOTE: DO NOT FLASH PhilZ recovery because it's NOT a standalone recovery. click the link below to download from my dropbox, if by any chance that dropbox decides to stop allowing you to download, just PM & I WILL send you a new link personally. philz.zip You can check the scripts/edit them to your hearts content, but there's nothing in them that will harm your PC, device, or your mom.. also the credits the one & only dev who built this recovery for us! is hroark13
Problems with building LineageOS 14.1 on my own
At the beginning, great thanks to Comzzmy13 for his work for official LineageOS. I don't know if it is suitable to post this thread here. If it is not that proper, please tell me! I want to build LineageOS on my computer and met some problems. I need some help now... Thanks all the guys coming into this thread! I followed the official guide to get all the sources, vendor, device, kernel from GitHub. But after running 'brunch libra'. after several minutes, errors occurred. Environment: Ubuntu 17.10 on a real machine (dual systems with windows 10) Tools should be enough but I'm not so sure and I just follow the guide. Firstly, just in case... Code: ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=7.1.2 LINEAGE_VERSION=14.1-20171214_170732-UNOFFICIAL-libra TARGET_PRODUCT=lineage_libra TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm64 TARGET_ARCH_VARIANT=armv8-a TARGET_CPU_VARIANT=cortex-a53 TARGET_2ND_ARCH=arm TARGET_2ND_ARCH_VARIANT=armv7-a-neon TARGET_2ND_CPU_VARIANT=cortex-a53.a57 HOST_ARCH=x86_64 HOST_2ND_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-4.13.0-17-generic-x86_64-with-Ubuntu-17.10-artful HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 HOST_BUILD_TYPE=release BUILD_ID=NJH47F OUT_DIR=/home/ippfcox/android/lineage/out ============================================ make: Entering directory '/home/ippfcox/android/lineage' ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=7.1.2 LINEAGE_VERSION=14.1-20171214_170732-UNOFFICIAL-libra TARGET_PRODUCT=lineage_libra TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm64 TARGET_ARCH_VARIANT=armv8-a TARGET_CPU_VARIANT=cortex-a53 TARGET_2ND_ARCH=arm TARGET_2ND_ARCH_VARIANT=armv7-a-neon TARGET_2ND_CPU_VARIANT=cortex-a53.a57 HOST_ARCH=x86_64 HOST_2ND_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-4.13.0-17-generic-x86_64-with-Ubuntu-17.10-artful HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 HOST_BUILD_TYPE=release BUILD_ID=NJH47F OUT_DIR=/home/ippfcox/android/lineage/out ============================================ Code: /home/ippfcox/android/lineage/out/build-lineage_libra.ninja is missing, regenerating... ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=7.1.2 LINEAGE_VERSION=14.1-20171214_170745-UNOFFICIAL-libra TARGET_PRODUCT=lineage_libra TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm64 TARGET_ARCH_VARIANT=armv8-a TARGET_CPU_VARIANT=cortex-a53 TARGET_2ND_ARCH=arm TARGET_2ND_ARCH_VARIANT=armv7-a-neon TARGET_2ND_CPU_VARIANT=cortex-a53.a57 HOST_ARCH=x86_64 HOST_2ND_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-4.13.0-17-generic-x86_64-with-Ubuntu-17.10-artful HOST_CROSS_OS=windows HOST_CROSS_ARCH=x86 HOST_CROSS_2ND_ARCH=x86_64 HOST_BUILD_TYPE=release BUILD_ID=NJH47F OUT_DIR=/home/ippfcox/android/lineage/out ============================================ The build log is too long so I just choose the error lines these seems not the key errors... Code: Checking build tools versions... find: ‘/home/ippfcox/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: 没有那个文件或目录 PRODUCT_COPY_FILES device/xiaomi/libra/audio/audio_effects.conf:system/etc/audio_effects.conf ignored. build/core/Makefile:54: Duplicate header copy: /home/ippfcox/android/lineage/out/target/product/libra/obj/include/time-services/time_genoff.h build/core/Makefile:54: Defined in: device/xiaomi/libra/time-services/Android.mk vendor/qcom/opensource/time-services/Android.mk The Chinese "没有那个文件或目录" == "No such file or dictionary" and then Code: make: Leaving directory '/home/ippfcox/android/lineage/kernel/xiaomi/msm8992' make: Entering directory '/home/ippfcox/android/lineage/kernel/xiaomi/msm8992' /home/ippfcox/android/lineage/kernel/xiaomi/msm8992/Makefile:801: *** 多个目标匹配。 停止。 Makefile:130: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 The Chinese "多个目标匹配。停止。" == "multiple target patterns. stop." and the last one Code: ninja: build stopped: subcommand failed. build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed make: *** [ninja_wrapper] Error 1 Please give me some advice! Thanks
I need more info, it is all error log? I use this guide to build lineageOS: https://wiki.lineageos.org/devices/libra/build Enviado desde mi Mi-4c mediante Tapatalk
groche97 said: I need more info, it is all error log? I use this guide to build lineageOS: https://wiki.lineageos.org/devices/libra/build Enviado desde mi Mi-4c mediante Tapatalk Click to expand... Click to collapse Yeah, this is also the guide I used. I will post the whole error log below, wait a moment.
@groche97 sorry for waiting so long. Something went wrong with my Internet connection... before building, I run repo sync. All the logs are attached below, 241 lines. Thanks!
All right....I will try to use Ubuntu 16.04 to build again...
Ippfcox said: All right....I will try to use Ubuntu 16.04 to build again... Click to expand... Click to collapse have you build kernel? i have same error
orfik said: have you build kernel? i have same error Click to expand... Click to collapse I think the error of mine is generated when building the kernel. Now I'm trying to build LineageOS 15.1, there is also this error... I will try again after some days. I have googled this error, maybe you can try to upgrade the build tools? I don't know exactly. And maybe you can just ask the author cozzmy13. But before that, I think we should try to fix by ourselves.
Ippfcox said: I think the error of mine is generated when building the kernel. Click to expand... Click to collapse Yes. And i have build kernel successfully. Change Makefile in kernel folder and build kernel for RR based on cm-14.1 I send you this Makefile in pm later. After work
orfik said: Yes. And i have build kernel successfully. Change Makefile in kernel folder and build kernel for RR based on cm-14.1 I send you this Makefile in pm later. After work Click to expand... Click to collapse Wow! You are great! Waiting for you
I have been experiencing the same kind of issues with the Ninja tool. It leaves the directory with no reason at all (OK, there has to be a reason for it to leave the directory or just encounter an error). I also used this command: export USE_NINJA=false And I think it uses the Java to build the ROM but still encounters errors and exits after 1 - 2 minutes into the build process. Not sure what is the issue or how to fix it. And it is not that I am waiting for the guys at Lineage to build the ROM for me, I wanted to build it for myself and help out. But keep having these errors and everyting goes to dust. I also tried building Nougat with the same issues. Off the record, I am building for Bacon, but the process is the same. Looking forward to new ideas/solutions/anything that can help us get past this step and successfully build the ROM.
i have remove ccach in Makefile,but in the end ,I encounter the error below [ 96% 647/668] Target userdata fs image: /home/zhj/code/LineageOs/out/target/product/libra/userdata.img Running: mkuserimg.sh -s /home/zhj/code/LineageOs/out/target/product/libra/data /home/zhj/code/LineageOs/out/target/product/libra/userdata.img ext4 data 12469648896 -D /home/zhj/code/LineageOs/out/target/product/libra/system -L data /home/zhj/code/LineageOs/out/target/product/libra/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin make_ext4fs -s -T -1 -S /home/zhj/code/LineageOs/out/target/product/libra/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin -L data -l 12469648896 -a data /home/zhj/code/LineageOs/out/target/product/libra/userdata.img /home/zhj/code/LineageOs/out/target/product/libra/data /home/zhj/code/LineageOs/out/target/product/libra/system Creating filesystem with parameters: Size: 12469645312 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: data Blocks: 3044347 Block groups: 93 Reserved block group size: 743 Created filesystem with 38/761856 inodes and 90385/3044347 blocks /home/zhj/code/LineageOs/out/target/product/libra/userdata.img maxsize=12730643904 blocksize=135168 total=149892064 reserve=128679936 [ 97% 654/668] Building Kernel make: Entering directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' GEN /home/zhj/code/LineageOs/out/target/product/libra/obj/KERNEL_OBJ/Makefile scripts/kconfig/conf --silentoldconfig Kconfig warning: (SND_SOC_APQ8074 && SND_SOC_MSM8994) selects SND_SOC_MSM_HDMI_CODEC_RX which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && FB_MSM_MDSS_HDMI_PANEL && (SND_SOC_MSM8974 || SND_SOC_APQ8084 || SND_SOC_MSM8994)) warning: (SND_SOC_APQ8074 && SND_SOC_MSM8994) selects SND_SOC_MSM_HDMI_CODEC_RX which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && FB_MSM_MDSS_HDMI_PANEL && (SND_SOC_MSM8974 || SND_SOC_APQ8084 || SND_SOC_MSM8994)) GEN /home/zhj/code/LineageOs/out/target/product/libra/obj/KERNEL_OBJ/Makefile CHK include/generated/uapi/linux/version.h CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost Using /home/zhj/code/LineageOs/kernel/xiaomi/libra as source for kernel CHK include/generated/utsrelease.h CALL /home/zhj/code/LineageOs/kernel/xiaomi/libra/scripts/checksyscalls.sh CHK include/generated/compile.h GZIP kernel/config_data.gz CHK kernel/config_data.h make[2]: 'arch/arm64/boot/Image' is up to date. make: Leaving directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' Building DTBs make: Entering directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost make[2]: Nothing to be done for 'dtbs'. make[2]: Nothing to be done for 'dtbs'. make: Leaving directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' [ 98% 657/668] Target boot image: /home/zhj/code/LineageOs/out/target/product/libra/boot.img FAILED: /home/zhj/code/LineageOs/out/target/product/libra/boot.img /bin/bash -c "(/home/zhj/code/LineageOs/out/host/linux-x86/bin/mkbootimg --kernel /home/zhj/code/LineageOs/out/target/product/libra/kernel --ramdisk /home/zhj/code/LineageOs/out/target/product/libra/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-5 buildvariant=userdebug" --os_version 8.1.0 --os_patch_level 2018-05-05 -2 --output /home/zhj/code/LineageOs/out/target/product/libra/boot.img ) && (size=\$(for i in /home/zhj/code/LineageOs/out/target/product/libra/boot.img; do stat --format "%s" "\$i" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo "\$size" ) )); printname=\$(echo -n "/home/zhj/code/LineageOs/out/target/product/libra/boot.img" | tr " " +); img_blocksize=135168; twoblocks=\$((img_blocksize * 2)); onepct=\$(((((69206016 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=\$((twoblocks > onepct ? twoblocks : onepct)); maxsize=\$((69206016 - reserve)); echo "\$printname maxsize=\$maxsize blocksize=\$img_blocksize total=\$total reserve=\$reserve"; if [ "\$total" -gt "\$maxsize" ]; then echo "error: \$printname too large (\$total > [69206016 - \$reserve])"; false; elif [ "\$total" -gt \$((maxsize - 32768)) ]; then echo "WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)"; fi )" usage: mkbootimg [-h] --kernel KERNEL [--ramdisk RAMDISK] [--second SECOND] [--cmdline CMDLINE] [--base BASE] [--kernel_offset KERNEL_OFFSET] [--ramdisk_offset RAMDISK_OFFSET] [--second_offset SECOND_OFFSET] [--os_version OS_VERSION] [--os_patch_level OS_PATCH_LEVEL] [--tags_offset TAGS_OFFSET] [--board BOARD] [--pagesize {2048,4096,8192,16384,32768,65536,131072}] [--id] [--dt DT] -o OUTPUT mkbootimg: error: unrecognized arguments: -2 ninja: build stopped: subcommand failed. 10:58:38 ninja failed with: exit status 1
Ippfcox said: Wow! You are great! Waiting for you Click to expand... Click to collapse Can you send me a copy of makefile? I also encountered this problem. Thank
orfik said: Yes. And i have build kernel successfully. Change Makefile in kernel folder and build kernel for RR based on cm-14.1 I send you this Makefile in pm later. After work Click to expand... Click to collapse can you send me a copy of makefile? I also encountered this problem. Thank
zhanyue1124 said: [ 96% 647/668] Target userdata fs image: /home/zhj/code/LineageOs/out/target/product/libra/userdata.img Running: mkuserimg.sh -s /home/zhj/code/LineageOs/out/target/product/libra/data /home/zhj/code/LineageOs/out/target/product/libra/userdata.img ext4 data 12469648896 -D /home/zhj/code/LineageOs/out/target/product/libra/system -L data /home/zhj/code/LineageOs/out/target/product/libra/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin make_ext4fs -s -T -1 -S /home/zhj/code/LineageOs/out/target/product/libra/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin -L data -l 12469648896 -a data /home/zhj/code/LineageOs/out/target/product/libra/userdata.img /home/zhj/code/LineageOs/out/target/product/libra/data /home/zhj/code/LineageOs/out/target/product/libra/system Creating filesystem with parameters: Size: 12469645312 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: data Blocks: 3044347 Block groups: 93 Reserved block group size: 743 Created filesystem with 38/761856 inodes and 90385/3044347 blocks /home/zhj/code/LineageOs/out/target/product/libra/userdata.img maxsize=12730643904 blocksize=135168 total=149892064 reserve=128679936 [ 97% 654/668] Building Kernel make: Entering directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' GEN /home/zhj/code/LineageOs/out/target/product/libra/obj/KERNEL_OBJ/Makefile scripts/kconfig/conf --silentoldconfig Kconfig warning: (SND_SOC_APQ8074 && SND_SOC_MSM8994) selects SND_SOC_MSM_HDMI_CODEC_RX which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && FB_MSM_MDSS_HDMI_PANEL && (SND_SOC_MSM8974 || SND_SOC_APQ8084 || SND_SOC_MSM8994)) warning: (SND_SOC_APQ8074 && SND_SOC_MSM8994) selects SND_SOC_MSM_HDMI_CODEC_RX which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && FB_MSM_MDSS_HDMI_PANEL && (SND_SOC_MSM8974 || SND_SOC_APQ8084 || SND_SOC_MSM8994)) GEN /home/zhj/code/LineageOs/out/target/product/libra/obj/KERNEL_OBJ/Makefile CHK include/generated/uapi/linux/version.h CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost Using /home/zhj/code/LineageOs/kernel/xiaomi/libra as source for kernel CHK include/generated/utsrelease.h CALL /home/zhj/code/LineageOs/kernel/xiaomi/libra/scripts/checksyscalls.sh CHK include/generated/compile.h GZIP kernel/config_data.gz CHK kernel/config_data.h make[2]: 'arch/arm64/boot/Image' is up to date. make: Leaving directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' Building DTBs make: Entering directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost make[2]: Nothing to be done for 'dtbs'. make[2]: Nothing to be done for 'dtbs'. make: Leaving directory '/home/zhj/code/LineageOs/kernel/xiaomi/libra' [ 98% 657/668] Target boot image: /home/zhj/code/LineageOs/out/target/product/libra/boot.img FAILED: /home/zhj/code/LineageOs/out/target/product/libra/boot.img /bin/bash -c "(/home/zhj/code/LineageOs/out/host/linux-x86/bin/mkbootimg --kernel /home/zhj/code/LineageOs/out/target/product/libra/kernel --ramdisk /home/zhj/code/LineageOs/out/target/product/libra/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-5 buildvariant=userdebug" --os_version 8.1.0 --os_patch_level 2018-05-05 -2 --output /home/zhj/code/LineageOs/out/target/product/libra/boot.img ) && (size=\$(for i in /home/zhj/code/LineageOs/out/target/product/libra/boot.img; do stat --format "%s" "\$i" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo "\$size" ) )); printname=\$(echo -n "/home/zhj/code/LineageOs/out/target/product/libra/boot.img" | tr " " +); img_blocksize=135168; twoblocks=\$((img_blocksize * 2)); onepct=\$(((((69206016 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=\$((twoblocks > onepct ? twoblocks : onepct)); maxsize=\$((69206016 - reserve)); echo "\$printname maxsize=\$maxsize blocksize=\$img_blocksize total=\$total reserve=\$reserve"; if [ "\$total" -gt "\$maxsize" ]; then echo "error: \$printname too large (\$total > [69206016 - \$reserve])"; false; elif [ "\$total" -gt \$((maxsize - 32768)) ]; then echo "WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)"; fi )" usage: mkbootimg [-h] --kernel KERNEL [--ramdisk RAMDISK] [--second SECOND] [--cmdline CMDLINE] [--base BASE] [--kernel_offset KERNEL_OFFSET] [--ramdisk_offset RAMDISK_OFFSET] [--second_offset SECOND_OFFSET] [--os_version OS_VERSION] [--os_patch_level OS_PATCH_LEVEL] [--tags_offset TAGS_OFFSET] [--board BOARD] [--pagesize {2048,4096,8192,16384,32768,65536,131072}] [--id] [--dt DT] -o OUTPUT mkbootimg: error: unrecognized arguments: -2 ninja: build stopped: subcommand failed. 10:58:38 ninja failed with: exit status 1 Click to expand... Click to collapse have you got the solution as I am also running into same error