[Q] Custom kernel compile error!! - Android Q&A, Help & Troubleshooting

Believe me, I have searched here and googled high and low to help ...
if i've searched wrong and you know where the post i'm looking for is i will be more than
happy to read it.. point me to it!!
That being said.
Last week, i played around with getting a custom recovery built for INQ Cloud Touch..
is a nice little phone for it's price but lacks devs!
After compiling - flashing recompiling re-flashing for almost a week and on the verge of giving up ...
i realized, searched and found flash_image ... come to find out custom compile of recovery
was fine, fastboot did not like my device and wasn't flashing it properly.
So flash_image got the custom recovery working as suppose to, able to backup/restore ...
Flash roms.. however there are no roms.. best i could do was try roms from devices close to
this one, with no luck!
So i decided i would try my hand at making a 2.3.7 gingerbread rom.
of course stock is froyo 2.2.1 and before i can make the rom.. i need a kernel for gingerbread.
So i got the cm-kernel source using this guide:
http wiki DOT cyanogenmod DOT com/wiki/Building_Kernel_from_source
(sry wasn't allowed to post links)
[EDIT]
pulled my .config file using both
/proc/config.tgz
and the included script to pull it from the boot.img
[/EDIT]
Now, i been trying to get kernel compiled for the last 5 days.. and like i said, no lack of searching and reading...
Had first error, forgot what it was now, but i got it fixed and compile went on.
for the last 4 days i been facing this bad boy and can't find a fix for this to save my life.
Code:
LD .tmp_vmlinux1
arm-eabi-ld: no machine record defined
arm-eabi-ld: no machine record defined
arch/arm/mach-msm/built-in.o: In function `parse_tag_msm_partition':
/home/orgwiz/android/cm-kernel/cm-kernel/arch/arm/mach-msm/nand_partitions.c:126: undefined reference to `msm_nand_data'
drivers/built-in.o: In function `msm_i2c_recover_bus_busy':
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:276: undefined reference to `msm_set_i2c_mux'
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:314: undefined reference to `msm_set_i2c_mux'
drivers/built-in.o: In function `msm_i2c_probe':
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:492: undefined reference to `msm_set_i2c_mux'
make: *** [.tmp_vmlinux1] Error 1
I have a notepad full of things i have enabled/disabled and restored to original trying to find what is missing or shouldn't be there!
And help would be GREATLY APPRECIATED!

---

Well, I have very little linux knowledges, so I don't know if I will be able to help you, anyway send me a PM if you still need help with that, because it's really interesting what you are doing. There is no roms for this phone, I could not even find the original one. I have this phone, INQ cloud touch, and I made a big mistake, I removed the INQFacebook.apk and many others that were flashed in the rom, without making any buckup (I know, I'm idiot).
The thing is that I've been looking for the apks or the original rom with no luck, to restore them in my phone, as I cannot do anything from the phone, but I still have adb access so I can flash any file. On the phone obviously always pops up a messaging like "Application INQ Launcher (com.inqmobile.launcher.core) closed unspectly. Force to Close". I guess because it's trying to load some of the INQ applications I deleted, like INQFacebook.
So if you know where I could get those files to restore them in my mobile or if you know any official rom that I can flash using CWM (ClockworkMod Recovery) it would be very nice.
The list of apps I deleted are:
from SYSTEM/APP
Spotify
Vringo
Shazam
Facebook
INQFacebook...
INQFacebook...
GoodWLM...
from DATA/APP
com.spotify...
com.shazam...
com.facebook...
com.spbu.myhub...

---

Hi,
Well, even if was there and I wrote it I didn't realize that the whole thing was the default launcher, I just installed a new and set it as default and now the phone is ****ing perfect, and without the applications that I didn't want to have.

---

orgwiz said:
Believe me, I have searched here and googled high and low to help ...
if i've searched wrong and you know where the post i'm looking for is i will be more than
happy to read it.. point me to it!!
That being said.
Last week, i played around with getting a custom recovery built for INQ Cloud Touch..
is a nice little phone for it's price but lacks devs!
After compiling - flashing recompiling re-flashing for almost a week and on the verge of giving up ...
i realized, searched and found flash_image ... come to find out custom compile of recovery
was fine, fastboot did not like my device and wasn't flashing it properly.
So flash_image got the custom recovery working as suppose to, able to backup/restore ...
Flash roms.. however there are no roms.. best i could do was try roms from devices close to
this one, with no luck!
So i decided i would try my hand at making a 2.3.7 gingerbread rom.
of course stock is froyo 2.2.1 and before i can make the rom.. i need a kernel for gingerbread.
So i got the cm-kernel source using this guide:
http wiki DOT cyanogenmod DOT com/wiki/Building_Kernel_from_source
(sry wasn't allowed to post links)
[EDIT]
pulled my .config file using both
/proc/config.tgz
and the included script to pull it from the boot.img
[/EDIT]
Now, i been trying to get kernel compiled for the last 5 days.. and like i said, no lack of searching and reading...
Had first error, forgot what it was now, but i got it fixed and compile went on.
for the last 4 days i been facing this bad boy and can't find a fix for this to save my life.
Code:
LD .tmp_vmlinux1
arm-eabi-ld: no machine record defined
arm-eabi-ld: no machine record defined
arch/arm/mach-msm/built-in.o: In function `parse_tag_msm_partition':
/home/orgwiz/android/cm-kernel/cm-kernel/arch/arm/mach-msm/nand_partitions.c:126: undefined reference to `msm_nand_data'
drivers/built-in.o: In function `msm_i2c_recover_bus_busy':
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:276: undefined reference to `msm_set_i2c_mux'
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:314: undefined reference to `msm_set_i2c_mux'
drivers/built-in.o: In function `msm_i2c_probe':
/home/orgwiz/android/cm-kernel/cm-kernel/drivers/i2c/busses/i2c-msm.c:492: undefined reference to `msm_set_i2c_mux'
make: *** [.tmp_vmlinux1] Error 1
I have a notepad full of things i have enabled/disabled and restored to original trying to find what is missing or shouldn't be there!
And help would be GREATLY APPRECIATED!
Click to expand...
Click to collapse
Hi orgwiz,
Bug INQ for the kernel sources they are legally obligated to release them because of the GPL. Once you have the source then you should have correct board drivers. The way embedded development works is that INQ wrote really specific drivers stock cyanogen kernel only has stuff for supported devices. So even if you build it, it likely won't boot on your device. In terms of building a new kernel you may be able to get away using the same kernel but updated init scripts you can still have a decent port like that but your YMMV (worst case you'll have trouble with 3D drivers but I'm pretty sure most of your hardware should work fine with out changes). Try building a CM userland and seeing if you can get it to boot as a first step (its going to be difficult but its a 100% possible I was able to do it with a an Eclair kernel). At worst case you'll have to back fit changes to the Froyo kernel you can look around github and cherry pick commits. If you adventurous the other options is to forward fit all of INQ's changes to the CM kernel.

---

There's a backup of the stock rom available if you google for "Porting INQ Cloud Touch" on the cyanogenmod forums (I can't post links yet)
I'm also trying to do some dev on this phone but have mostly given up because I can't get anything to boot and I don't know of any way to get any form of debug messages. If anyone wants to help, let me know.
I didn't know that they were required to release the kernel sources, that will surely help so I've sent them an email.

---

This was my first android. It was a good little phone. But I killed it within a month. I had it rooted ( didn't make a backup ), was using a file explorer, and my thumb twitched deleting something the phone needed. The only thing I can get from it is emergency mode and adb mode when connected to the computer. I spent so much time looking for either an original Canadian rom or at least a custom one I could try to flash. I gave up eventually and moved on. I would still like to revive that droid if I could. Mainly to prove it ain't dead. lol. I'll keep checking in, good luck with your project. :good:

---

Error While Compiling Kernel Of REDMI 1s
Code:
[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/input/touchscreen/ft5x06_ts.o
drivers/input/touchscreen/ft5x06_ts.c: In function 'ft5x06_get_factory_id':
drivers/input/touchscreen/ft5x06_ts.c:432:45: warning: 'ft5336_bootloader_ver' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: ft5x06_ts.c:432
make[3]: *** [drivers/input/touchscreen/ft5x06_ts.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2