• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] kernel source code won't build

not a problem, yeah i got an image compiled last night finally but it wouldn't boot. not sure what I'm doing wrong here. trying again as we speak
 
Yup, same here. We're obviously missing something, I just don't know what. Glad you were able to get the kernel to build though.
 
after building it the second time it also compile the modules as well, but the original boot.img is around 16mb and my new boot.img is much smaller at around 4.1mb the zImage files for both kernels are the same size though. so where missing something for sure
 
Well I got a heck of an output: make -j8 ARCH=arm CROSS_COMPILE=$CROSS_COMPILE HOSTLD scripts/kconfig/conf - Pastebin.com

Problem:
Code: 
  CC      arch/arm/mach-msm/acpuclock-7x30.o
arch/arm/mach-msm/clock-7x30.c: In function 'msm_clk_soc_init':
arch/arm/mach-msm/clock-7x30.c:1262: error: ri_list causes a section type conflict
make[1]: *** [arch/arm/mach-msm/clock-7x30.o] Error 1
make[1]: *** Waiting for unfinished jobs....
  CC      fs/ext4/balloc.o
  CC      net/ipv4/tcp_output.o
  CC      net/netfilter/nf_conntrack_extend.o
  CC      net/sched/sch_mq.o
  CC      drivers/input/touchscreen/SynaUpgrade.o
make[1]: *** wait: No child processes.  Stop.
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....

:(
 
use the old ndk_r5c 4.4.0 toolchain and use

export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:~/path to toolchain/toolchain/arm-eabi-4.4.0/bin/

http://dl.google.com/android/ndk/android-ndk-r5c-linux-x86.tar.bz2

extract it anywhere and enter the path to the bin folder to export PATH=$PATH:Building the kernel works best for me with make menuconfig command

I might take a crack at cyanogenmod and help you out a bit snake
 
I believe its supposed to be built with 4.3.3 if that's what it said on the stock warp for 'gcc version' but I'll try anyhow
 
I spoke with sebastian and he said the only way he could get it to buil;d was with the 4.4.0 toolchain from NDK_r5c. i tried it and what do you know it worked. now i just have to figure out what to do with the modules and how to get it to actually boot lol

Overclock dropped to 1.4Ghz in-case of stability issues

EDIT: Forgot to mention Sebastian is going to send me the kernel he built.... Lets see if it works!
 
I'll say something to him, and see what he says hopefully he can help us a little more

Got a reply from sebastian on twitter. @shinru2004: I'll swing by later today once I get home...
 
Well I got further, and but still no zImage, no errors except at the end when it was supposed to spit out the zImage, it said the build_io file not found. I used the toolchain from the ndk 4.4.3 anyone have any ideas?
 
Don't know how much help I'll be, but here are my thoughts. From what I can tell, build_io is probably created during the build process and not a static file so it's probably not a PATH issue. Would suggest trying the build using stock kernel settings if you're not already. Eliminate any unneeded complexity until you know the build process works. Also I assume you did this, but you did specify ARCH=ARM in the command line right?
 
Stock kernel with the config, fromphone
Make ARCH=arm CROSS_COMPILE=$COMPILER -j 8
 
Said file not found. Supposed to be in /arch/arm/msm_mach directory I believe
 
I don't see any "build-io" files on my system in that dir. I do see a built-in.o file though. So, if build-io is the correct name, then it must be generated at the time of the build.

As a side note, is $COMPILER your variable name? Usually it's $CCOMPILER. Just want to make sure it's not a typo in your command line. I don't think it really matters what you name it so long as the variable name matches the CROSS_COMPILE value in the command line.
 
yeah, but I was just asking you to confirm what variable the toolchain path was assigned to. $COMPILER or $CCOMPILER. (just in case there was a typo in your command line)
 
I have it set to $CCOMPILER I also have other toolchain set similarly like $CCOMPILER1 and so on
 
downthemachine said:
Stock kernel with the config, fromphone
Make ARCH=arm CROSS_COMPILE=$COMPILER -j 8
Click to expand...

downthemachine said:
I have it set to $CCOMPILER I also have other toolchain set similarly like $CCOMPILER1 and so on
Click to expand...
Gotcha. Your previous command line just had $COMPILER (only 1 "C") so that's what made me question if there was a typo in the command line. If you used $COMPILER in the kernel build command line, it probably didn't use the toolchain that you wanted to use. Maybe your previous post just had a typo too. I dunno. Just something to verify when building.
 
No typo, I ran it four times a dbl checked my work, and and yes it was the file built_in.o but I can't seem to Locate it in the directory that it said not found, which was arch/arm/msm_mach and the funny part was there were no other errors, as got to the point where it was supposed to make the zImage errored. I tried with the ignore command -i same results
 
JBrd400 said:
Gotcha. Your previous command line just had $COMPILER (only 1 "C") so that's what made me question if there was a typo in the command line. If you used $COMPILER in the kernel build command line, it probably didn't use the toolchain that you wanted to use. Maybe your previous post just had a typo too. I dunno. Just something to verify when building.
Click to expand...

I see what I meant, i'm at work on tapatalk it autocorrected me :)

Ha and I just found the darn edit in tapatalk so I can stop multiposting
 
Okay, so your command line should be good. The fact that the built_in.o file exists on my system and not yours sounds like ther may be a problem with the kernel source files. Did you merge all the zte kernel source zip files together before extracting the kernel folder?
 
Ya, I think I did. Well it extracted to separate files. Then I extracted it again and it was on file, then extracted that and it was all the source. I guess I don't understand the merge part?
 
Okay, essentially Zte has split the kernel folder into multiple 7zip files and then taken each of those files and zipped them. So you have to extract the 7zip files from each zip and re-join all the 7zip files together again to get the full kernel folder. Here's how I did it. (assumes you're using linux)

1. Save all the Zte kernel .zip files to a folder somewhere.
2. Create a subfolder in there and extract all the 7zip files to the subfolder.
3. Browse to the subfolder with terminal and execute the following command:
cat kernel_roamer.7z.0* >> new_kernel.7z
4. Open the new_kernel.7z file with your file manager and drill down a couple times until you see the kernel folder. Once you find it, extract it to wherever location you want.

If you use Windows, you can just use the actual 7-zip program to re-combine all the 7zip files.

Hope that helps. If you still have questions, just ask...
 
Oh I see, well I did it in Linux, I don't remember the results, it was a while ago, but I also extracted them on my windows computer and it said there was a bunch of errors, so when I get done with work I'll try it again, thanks for the help!
 
You must log in or register to reply here.
Back
Top Bottom