[DEV] Porting kernel 3.10.x to d2 for Lollipop

[zachf714]

Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!

Build currently hangs at this:

host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1

#### make failed to build some targets (01:19 (mm:ss)) ####

Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night

your problems are that d2 uses -caf hardware repos and you are trying to compile with the stock aosp qcom hardware repos. You will need to wait for the -caf repos to build. You removed the liblights from msm8960-common right ? yea you dont want to do that, the samsung msm8960 devices use a specific version of liblights,

Also relating to the kernel, hammerhead and flo are shipping with a 3.4 kernel as well as grouper is shipping with a 3.1 kernel for lollipop so there is no "need" to update the kernel

 

[ztotherad]

i have a feeling in all of this that the note 2 variants are going to have a much harder time to be able to adapt to lollipop since we're running a much older kernel than the d2lte variants.. lol. but it is nice to see progress for older devices!

 

[Ivan_Meler]

i have a feeling in all of this that the note 2 variants are going to have a much harder time to be able to adapt to lollipop since we're running a much older kernel than the d2lte variants.. lol. but it is nice to see progress for older devices!

Its not related to kernel we are running now, its related to our platform smdk4412 and smdk4412 is hell for development

 

[Restl3ss]

Its not related to kernel we are running now, its related to our platform smdk4412 and smdk4412 is hell for development

At least you're not running intel clovertrail. Me and a few others have been trying to port cm11 to the Galaxy Tab 3 10.1 for months.

 

[Restl3ss]

your problems are that d2 uses -caf hardware repos and you are trying to compile with the stock aosp qcom hardware repos. You will need to wait for the -caf repos to build. You removed the liblights from msm8960-common right ? yea you dont want to do that, the samsung msm8960 devices use a specific version of liblights,

Also relating to the kernel, hammerhead and flo are shipping with a 3.4 kernel as well as grouper is shipping with a 3.1 kernel for lollipop so there is no "need" to update the kernel

Okay, so I've readded liblights to msm8960-common and changed up sepolicy a bit so it doesn't clash. Also grabbed hardware/qcom and hardware/samsung from the CM11 source and added them to the build.
I've also changed / added a couple .mk files to the device tree so that it now builds as aosp_d2lte-userdebug instead of full_d2lte-eng.

After the fact I ran make again and the build went on for a bit longer (past where I was) but is now halted at

Export includes file: frameworks/native/services/batteryservice/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libbatteryservice_intermediates/export_includes
Export includes file: frameworks/native/libs/binder/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libbinder_intermediates/export_includes
Export includes file: bootable/recovery/minui/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes
Export includes file: external/libpng/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libpng_intermediates/export_includes
Export includes file: external/zlib/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libz_intermediates/export_includes
Export includes file: system/core/libutils/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libutils_intermediates/export_includes
make: *** No rule to make target 'out/target/product/d2lte/obj/STATIC_LIBRARIES/libhealthd.qcom_intermediates/export_includes', needed by 'out/target/product/d2lte/obj/EXECUTABLES/healthd_intermediates/import_includes'.  Stop.

#### make failed to build some targets (38:18 (mm:ss)) ####

[email protected]:~/aosp$

Any ideas?

I'm about to head to bed, will continue tomorrow.

edit: I had a last minute idea and manually added the missing file from the cm11 finished build, the build is now moving again. Still though, might be indicative of a larger problem. We'll see in the A.M

edit 2: Now it's stuck at this;

make: *** No rule to make target 'NOTICE-TARGET-STATIC_LIBRARIES-libhealthd.qcom', needed by 'out/target/product/d2lte/root/sbin/healthd'.  Stop.

#### make failed to build some targets (01:49 (mm:ss)) ####

 

[zachf714]

Okay, so I've readded liblights to msm8960-common and changed up sepolicy a bit so it doesn't clash. Also grabbed hardware/qcom and hardware/samsung from the CM11 source and added them to the build.
I've also changed / added a couple .mk files to the device tree so that it now builds as aosp_d2lte-userdebug instead of full_d2lte-eng.

After the fact I ran make again and the build went on for a bit longer (past where I was) but is now halted at

Export includes file: frameworks/native/services/batteryservice/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libbatteryservice_intermediates/export_includes
Export includes file: frameworks/native/libs/binder/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libbinder_intermediates/export_includes
Export includes file: bootable/recovery/minui/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes
Export includes file: external/libpng/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libpng_intermediates/export_includes
Export includes file: external/zlib/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libz_intermediates/export_includes
Export includes file: system/core/libutils/Android.mk -- out/target/product/d2lte/obj/STATIC_LIBRARIES/libutils_intermediates/export_includes
make: *** No rule to make target 'out/target/product/d2lte/obj/STATIC_LIBRARIES/libhealthd.qcom_intermediates/export_includes', needed by 'out/target/product/d2lte/obj/EXECUTABLES/healthd_intermediates/import_includes'.  Stop.

#### make failed to build some targets (38:18 (mm:ss)) ####

[email protected]:~/aosp$

Any ideas?

I'm about to head to bed, will continue tomorrow.

edit: I had a last minute idea and manually added the missing file from the cm11 finished build, the build is now moving again. Still though, might be indicative of a larger problem. We'll see in the A.M

edit 2: Now it's stuck at this;

make: *** No rule to make target 'NOTICE-TARGET-STATIC_LIBRARIES-libhealthd.qcom', needed by 'out/target/product/d2lte/root/sbin/healthd'.  Stop.

#### make failed to build some targets (01:49 (mm:ss)) ####

You know the cm manifest dropped right, you are going to have to hack pure aosp to h*ll to get it booting and working. I work with the d2 maintainers on bring ups and even on cm there is hacking to be done. If you can't write C and CPP and or solve build errors you will not be able to do such a big os bring up.
I don't want to clutter a kernel thread anymore with compilation help

Sent from my SCH-I535 using Tapatalk

 

[Ivan_Meler]

At least you're not running intel clovertrail. Me and a few others have been trying to port cm11 to the Galaxy Tab 3 10.1 for months.

Yeah i know Intel+cyanogenmod didnt go so well so far

 

[ztotherad]

Its not related to kernel we are running now, its related to our platform smdk4412 and smdk4412 is hell for development

samsung really knows how to screw things up for third party developers don't they? lol.

 

[LLStarks]

Just a thought, if you guys need faster communication, there's always the IRC channel. It's very active.