[Droid] Building CM6 from source Error - Motorola Droid and Milestone General

Hi, I posted this at the Cyanogen forums - but I figured I would ask here too:
I am trying to build CM6 from source. I have followed the Wiki but I am getting this error:
Code:
Finding NOTICE files: out/target/product/sholes/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/sholes/obj/NOTICE.html
Target system fs image: out/target/product/sholes/obj/PACKAGING/systemimage_unopt_intermediates/system.img
Install system fs image: out/target/product/sholes/system.img
out/target/product/sholes/system.img+ total size is 152454720
error: out/target/product/sholes/system.img+ too large (152454720 > [151793664 - ])
make: *** [out/target/product/sholes/system.img] Error 1
make: *** Deleting file `out/target/product/sholes/system.img'
Any help would be great.. I have copied all of the proprietary files and have the latest source from the git repository.

Related

For devs .. compiling boot.img error

Hi Devs ,
i've been trying to build new LS nightly .. and im using this kernel https://github.com/LiquidSmooth-Devices/android_kernel_sony_msm8974 & device tree https://github.com/LiquidSmooth-Devices/android_device_sony_honami
so i got this error
Code:
DTB combiner:
Input directory: '/home/teamliquid/Ahmed/out/target/product/honami/obj/KERNEL_OBJ/arch/arm/boot/'
Output file: '/home/teamliquid/Ahmed/out/target/product/honami/dt.img'
=> Found 0 unique DTB(s)
error: could not load device tree image '/home/teamliquid/Ahmed/out/target/product/honami/dt.img'
make: *** [/home/teamliquid/Ahmed/out/target/product/honami/boot.img] Error 1
make: *** Waiting for unfinished jobs....
any ideas ?

[Q] Headers location missing during the build process

Hi Team,
I am trying to build the ROM from AOSP Source based on 5.1.1.
Till now the build was going fine but now I am facing issue with compilation errors.
The QCOM stuff creating these error because each files in the folder hardware/qcom/display/msm8974 missing the reference to compiler header file/location.
So I don't want to amend each reference to point specifically. I know where the files are located but compiler not picking it up.
E.G: #include <media/msm_media_info.h>
All the stuff available on >> hardware/qcom/msm8x74
Can someone please guide me like which ENV variable I need to check?? or which .mk file I need to amend ??
*********************************
target thumb C++: libmemalloc <= hardware/qcom/display/msm8974/libgralloc/ionalloc.cpp
target thumb C++: libmemalloc <= hardware/qcom/display/msm8974/libgralloc/alloc_controller.cpp
hardware/qcom/display/msm8974/libgralloc/alloc_controller.cpp:41:34: fatal error: media/msm_media_info.h: No such file or directory
#include <media/msm_media_info.h>
^
compilation terminated.
build/core/binary.mk:620: recipe for target 'out/target/product/cancro/obj/SHARED_LIBRARIES/libmemalloc_intermediates/alloc_controller.o' failed
make: *** [out/target/product/cancro/obj/SHARED_LIBRARIES/libmemalloc_intermediates/alloc_controller.o] Error 1
make: *** Waiting for unfinished jobs....
*********************************

AOSPA for Xperia SP

Hello,
I'm trying to build AOSPA for Xperia SP but getting this error:
Code:
Made recovery image: out/target/product/huashan/recovery.img
Target build info: out/target/product/huashan/system/build.prop
find: ‘out/target/product/huashan/recovery/root/res’: No such file or directory
cat: out/target/product/huashan/recovery.id: No such file or directory
build/tools/generate-notice-files.py out/target/product/huashan/obj/NOTICE.txt out/target/product/huashan/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" out/target/product/huashan/obj/NOTICE_FILES/src
zip error: Nothing to do! (out/target/product/huashan/system/etc/recovery-resource.dat)
make: *** [out/target/product/huashan/system/etc/recovery-resource.dat] Error 12
make: *** Waiting for unfinished jobs....
Does AOSP based roms need some additional commits to be able to build ? I hadn't such problems with Lineage and Vanir ROMs.
Here is my roomservice.xml file and full terminal output.
Thanks in advance for any help

How to compile Samsung S10 kernel for Exynos 9820?

I tried the following:
Download toolchain from https://android.googlesource.com/pl....9/+/e54105c9f893a376232e0fc539c0e7c01c829b1e
Download clang-4639204
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
sudo apt-get install flex bison
sudo apt-get install libelf-dev
export CROSS_COMPILE=/home/gilius/Desktop/tool/bin/aarch64-linux-android-
export ARCH=arm64
enter the 9820 directory
sudo -i
make xynos9820-beyond2lte_defconfig
make -j10
Am getting the following errors:
Code:
arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
arch/arm64/Makefile:57: Detected assembler with broken .inst; disassembly will be unreliable
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
CHK include/config/kernel.release
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
make: *** [Makefile:1244: prepare-compiler-check] Error 1
make: *** Waiting for unfinished jobs....
Hi,
for me : sudo ln -s /usr/lib/libtinfo.so /usr/lib/libtinfo.so.5 did the trick but I am now stuck with some assembly instructions "not existing" errors when compiling arch/arm64/kernel/vdso/gettimeofday.S
did you made any progress?
Update : linking libtinfo.so.6 to libtinfo.so.5 solved it but also failed with :
scripts/selinux/genheaders/genheaders.c:19:
./security/selinux/include/classmap.h:251:2: erreur: #error New address family defined, please update secclass_map.
251 | #error New address family defined, please update secclass_map.
| ^~~~~
make[3]: *** [scripts/Makefile.host:102: scripts/selinux/genheaders/genheaders] Error 1
make[2]: *** [scripts/Makefile.build:673: scripts/selinux/genheaders] Error 2
make[1]: *** [scripts/Makefile.build:673: scripts/selinux] Error 2
make: *** [Makefile:607: scripts] Error 2
I am currently trying it on archlinux and the ncurses5-compat-libs package didn't put a new library in my path I will try later on another distro see if it's just a library error.
Update 2 :
Compiled fine using rhel 8, I had to install ncurses compat libs and create a symbolic link from python2 to python in my $PATH.
Does it boot?
Does your kernel boot?
Mine, keep stuck at Samsung logo
Akugila said:
Does your kernel boot?
Mine, keep stuck at Samsung logo
Click to expand...
Click to collapse
Non, I can't even go further the unlocked warning screen, but my repacking of the image is wrong, my new image is always lighter than the original, I am using magiskboot to do it. How are you doing it ?
try AIK
shmsh9 said:
Non, I can't even go further the unlocked warning screen, but my repacking of the image is wrong, my new image is always lighter than the original, I am using magiskboot to do it. How are you doing it ?
Click to expand...
Click to collapse
Ahh, fool me. it's stuck at warning screen too (forgot there are another samsung logo during boot)
I use AIK [https://forum.xda-developers.com/showthread.php?t=2073775] for packing, the size is the same with original (I use "Image" file)
kernel build error: expected parameter declarator
Did you get these compilation errors?
In file included from kernel/bounds.c:10:
In file included from ./include/linux/page-flags.h:10:
In file included from ./include/linux/bug.h:5:
In file included from ./arch/arm64/include/asm/bug.h:37:
In file included from ./include/asm-generic/bug.h:16:
In file included from ./include/linux/kernel.h:14:
./include/linux/printk.h:149:24: error: expected parameter declarator
static inline __printf(1, 2) __cold
^
./include/linux/printk.h:149:24: error: expected ')'
./include/linux/printk.h:149:23: note: to match this '('
static inline __printf(1, 2) __cold
^
./include/linux/printk.h:149:23: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]
static inline __printf(1, 2) __cold
^
void
./include/linux/printk.h:149:29: error: expected ';' after top level declarator
static inline __printf(1, 2) __cold
^
Linaro 4.9.4 aarch64-linux-gnu compiler tools for S10 5G kernel build
floor51 said:
Did you get these compilation errors?
In file included from kernel/bounds.c:10:
In file included from ./include/linux/page-flags.h:10:
In file included from ./include/linux/bug.h:5:
In file included from ./arch/arm64/include/asm/bug.h:37:
In file included from ./include/asm-generic/bug.h:16:
In file included from ./include/linux/kernel.h:14:
./include/linux/printk.h:149:24: error: expected parameter declarator
static inline __printf(1, 2) __cold
^
./include/linux/printk.h:149:24: error: expected ')'
./include/linux/printk.h:149:23: note: to match this '('
static inline __printf(1, 2) __cold
^
./include/linux/printk.h:149:23: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]
static inline __printf(1, 2) __cold
^
void
./include/linux/printk.h:149:29: error: expected ';' after top level declarator
static inline __printf(1, 2) __cold
^
Click to expand...
Click to collapse
I found that using the Linaro 4.9.4 aarch64-linux-gnu compiler tools solved this:
https://releases.linaro.org/compone...4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz
I was previously using the toolchain that is in ianmacd's github repo here:
https://github.com/ianmacd/beyond2l...p/gcc-cfp-jopp-only/aarch64-linux-android-4.9
I changed this:
#CROSS_COMPILE ?= $(srctree)/toolchain/gcc-cfp/gcc-cfp-jopp-only/aarch64-linux-android-4.9/bin/aarch64-linux-android-
...to:
CROSS_COMPILE ?= ~/dev/projects/android/kernel/gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
I also used Linaro for CLANG_TRIPLE.
And I used clang for CC:
CC = ~/dev/projects/android/kernel/clang-4639204/bin/clang
...from here:
https://android.googlesource.com/pl...archive/android-9.0.0_r1/clang-4639204.tar.gz
All that info would have helped me a lot anyway. Hope it helps someone. Not that I've tried the image on device yet.
Hey,
I have managed to build the kernel by following the instructions in the samsung readme.
Code:
$ export ANDROID_MAJOR_VERSION=p
$ make ARCH=arm64 exynos9820-d2s_defconfig
$ make ARCH=arm64
I end up with an Image file and Image.gz with the same Image file inside. I'm not sure if this has built correctly as people talk about being able to use Android kitchen or similar unpacker to unpack and repack the img file. With the Image file I receive it is incompatible with Android Kitchen and another Perl unpacker I have tried.
When you compile your kernel do you get an Image.img file? Or the same as me, just Image, and if so, how do you make it usable?
JPNZ4 said:
Hey,
I have managed to build the kernel by following the instructions in the samsung readme.
Code:
$ export ANDROID_MAJOR_VERSION=p
$ make ARCH=arm64 exynos9820-d2s_defconfig
$ make ARCH=arm64
I end up with an Image file and Image.gz with the same Image file inside. I'm not sure if this has built correctly as people talk about being able to use Android kitchen or similar unpacker to unpack and repack the img file. With the Image file I receive it is incompatible with Android Kitchen and another Perl unpacker I have tried.
When you compile your kernel do you get an Image.img file? Or the same as me, just Image, and if so, how do you make it usable?
Click to expand...
Click to collapse
glad to hear that you could build the kernel.
could you please elaborate which build env you used and which version?
make clean destroys my build env and i needed some patches to make it even compile in the first place.
could you run the kernel successfully on the device?

Having issues compiling kernel...

I have built kernels before, but this one just spits out error after error after error.. very annoying and nothing I found seems to help.
Currently stuck with these errors and don't know how to solve them, any help is appreciated:
Code:
kperfmon_DUMMY="perflog.h file is missing."
cp: cannot stat '../../../system/core/liblog/include/log/perflog.h': No such file or directory
kperfmon_DUMMY=""
kperfmon_DUMMY=""
CC drivers/kperfmon/ologk.o
AR drivers/kperfmon/built-in.o
AR drivers/built-in.o
make[2]: *** No rule to make target '/home/dpi/qb5_8814/workspace/P4_1716/buildscript/tools/pil_splitter.py', needed by 'firmware/five/five.signed'. Stop.
/home/seth/AndroidKernel/G977p/Makefile:1165: recipe for target 'firmware' failed
make[1]: *** [firmware] Error 2
make[1]: Leaving directory '/home/seth/AndroidKernel/G977p/output'
Makefile:146: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
The missing perflog.h file is a crucial component for the build process.
To resolve, locate the perflog.h:
find /path/to/starting/directory -type f -name "perflog.h"
Replace /path/to/starting/directory with the appropriate root directory to begin the search. Once located, transfer the file to the expected destination.
If the file is absent, examine the kernel source code repository. If the file is accessible, download it and place it in the required location.
The second issue pertains to a missing rule needed to create the target '/home/dpi/qb5_8814/workspace/P4_1716/buildscript/tools/pil_splitter.py'. This indicates that the build process anticipates a rule to generate the target file, but the rule is not specified in the Makefile.
To resolve this issue, take the following steps:
- Determine whether the target file (pil_splitter.py) exists within your system. If not, obtain it from the kernel source code repository.
- If the file is present, verify that the Makefile includes the appropriate rule for constructing the target file. It may be necessary to add or modify the rule in the Makefile, ensuring it references the correct dependencies and commands.

Categories

Resources