[need dev help] CM10.2 build error - Xperia SP Q&A, Help & Troubleshooting

Hello guys,
Today I tried building a rom from source for my xperia sp but i got an error and I don't know how to fix it: so I issued the command brunch huashan after everything went well and it took a minute but then it said this:
Import includes file: /home/noahvt/android/system/out/target/product/huashan/obj/SHARED_LIBRARIES/libgccdemangle_intermediates/import_includes
make: *** No rule to make target `/home/noahvt/android/system/out/target/product/huashan/obj/lib/libtime_genoff.so', needed by `/home/noahvt/android/system/out/target/product/huashan/obj/SHARED_LIBRARIES/libutils_intermediates/LINKED/libutils.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/noahvt/android/system/out/target/product/huashan/obj/SHARED_LIBRARIES/libz_intermediates/import_includes
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
I tried doing breakfast huashan and then brunch huashan and that removed some random errors but I still got this:
make: *** No rule to make target `/home/noahvt/android/system/out/target/product/huashan/obj/lib/libtime_genoff.so', needed by `/home/noahvt/android/system/out/target/product/huashan/obj/SHARED_LIBRARIES/libutils_intermediates/LINKED/libutils.so'. Stop.
make: *** Waiting for unfinished jobs....
Can anyone help me i really want to build a rom for this phone
thanks in advance,
noahvt

Related

Help Inserting Multi Touch Patch Into Kernel

I've combined different features from Cyanogen's and JesusFreke's kernel .config files (from /proc/config.gz) into a git clone of android-msm-2.6.29 from android.git.kernel.org. The reason is that for some reason suid does not work properly when running debian as a non-root user on my G1 with Cyanogen's kernels. However it does with JesusFreke's. While I was able to fix that problem, and keep Cyanogens optimizations, I also unfortunately lost Cyanogen's kernel support for multitouch. I assumed this is because he is using a patched version of the synaptics touchpad driver, whereas I was not. So, I tried to download this Kernel Patch (http://web.mit.edu/~luke_h/www/MultiTouchV4/src/KernelPatch.zip), which is what I believe Cyanogen used. However, after replacing the target file with the included one, the make fails with the following:
...
CC drivers/input/touchscreen/synaptics_i2c_rmi.o
drivers/input/touchscreen/synaptics_i2c_rmi.c:31:1: warning: "swap" redefined
In file included from include/linux/cache.h:4,
from include/linux/time.h:7,
from include/linux/stat.h:60,
from include/linux/module.h:10,
from drivers/input/touchscreen/synaptics_i2c_rmi.c:18:
include/linux/kernel.h:483:1: warning: this is the location of the previous definition
drivers/input/touchscreen/synaptics_i2c_rmi.c: In function 'synaptics_ts_probe':
drivers/input/touchscreen/synaptics_i2c_rmi.c:513: error: 'struct i2c_client' has no member named 'driver_name'
drivers/input/touchscreen/synaptics_i2c_rmi.c: At top level:
drivers/input/touchscreen/synaptics_i2c_rmi.c:639: warning: initialization from incompatible pointer type
make[3]: *** [drivers/input/touchscreen/synaptics_i2c_rmi.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
...
Any thoughts on where to proceed from here?

[Q] Compilation problem on Nexus One build

I am trying to compile Android from the source for my Nexus One. I pretty much followed all instructions from here: http://forum.xda-developers.com/showthread.php?t=899674
Though the instructions are for Gingerbread, I don't really see much of a difference for Froyo. After I do a "make -j4", the following error is thrown:
Code:
Install: out/target/product/passion/system/lib/libmedia.so
target SharedLib: libstagefright_foundation (out/target/product/passion/obj/SHARED_LIBRARIES/libstagefright_foundation_intermediates/LINKED/libstagefright_foundation.so)
target SharedLib: libstagefright_color_conversion (out/target/product/passion/obj/SHARED_LIBRARIES/libstagefright_color_conversion_intermediates/LINKED/libstagefright_color_conversion.so)
target SharedLib: libaudio (out/target/product/passion/obj/SHARED_LIBRARIES/libaudio_intermediates/LINKED/libaudio.so)
target SharedLib: libaudiopolicy (out/target/product/passion/obj/SHARED_LIBRARIES/libaudiopolicy_intermediates/LINKED/libaudiopolicy.so)
target SharedLib: libcameraservice (out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/LINKED/libcameraservice.so)
prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/CameraService.o: in function android::CameraService::getCameraInfo(int, android::CameraInfo*):frameworks/base/services/camera/libcameraservice/CameraService.cpp:109: error: undefined reference to 'HAL_getCameraInfo'
prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/CameraService.o: in function android::CameraService::CameraService():frameworks/base/services/camera/libcameraservice/CameraService.cpp:75: error: undefined reference to 'HAL_getNumberOfCameras'
prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/CameraService.o: in function android::CameraService::CameraService():frameworks/base/services/camera/libcameraservice/CameraService.cpp:75: error: undefined reference to 'HAL_getNumberOfCameras'
prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/CameraService.o: in function android::CameraService::connect(android::sp<android::ICameraClient> const&, int):frameworks/base/services/camera/libcameraservice/CameraService.cpp:148: error: undefined reference to 'HAL_openCameraHardware'
prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/CameraService.o: in function android::CameraService::connect(android::sp<android::ICameraClient> const&, int):frameworks/base/services/camera/libcameraservice/CameraService.cpp:154: error: undefined reference to 'HAL_getCameraInfo'
collect2: ld returned 1 exit status
make: *** [out/target/product/passion/obj/SHARED_LIBRARIES/libcameraservice_intermediates/LINKED/libcameraservice.so] Error 1
make: *** Waiting for unfinished jobs....
Note: cts/tools/dx-tests/src/dxc/junit/opcodes/invokeinterface/jm/T_invokeinterface_1.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
compiling all jasmin (*.j)
compiling all .cfh files into .class files
generating Main_*.java files reading from cts/tools/dx-tests writing to out/host/darwin-x86/obj/EXECUTABLES/dx-tests_intermediates/mainfiles
using java src:cts/tools/dx-tests/src
Collecting all junit tests...
Time: 0.025
OK (0 tests)
Can someone please help me resolve this issue?
If you want to compile Froyo - use a different guide. Either from CM6 page or from Android SDK explanations.
You're failing on library incompatibilities, specifically Camera lib - but since I don't know, what's the source core you're running (Froyo or Gingerbread repo), it's hard to say how to fix it. If you're following the guide in your post completely and compiling GB - you probably missed the "Fix Camera" part.
My bad! You're right.. There was the fix right at the bottom of that article. Thank you for pointing it out. Everything works properly..

[Q] Problem with compiling for Paranoid - Oliver sources

I'm trying to compile the OliverG96 sources to work with Paranoid and i have error, maybe someone have it and know a solution?
Code:
target Dex: CalendarProvider
frameworks/opt/telephony/../../../device/samsung/golden/ril/SamsungU8500RIL.java:434: cannot find symbol
symbol : variable RIL_REQUEST_ENTER_DEPERSONALIZATION_CODE
location: class com.android.internal.telephony.SamsungU8500RIL
case RIL_REQUEST_ENTER_DEPERSONALIZATION_CODE: ret = responseInts(p); break;
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
make: *** [/home/projects/android/system/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....

[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....
*********************************

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