Kernel compilation 2.6.35

Some time ago, ZTE released the kernel source code 35 of small V, and then downloaded it. It was prepared to compile it for a while. It was busy and dragged on this week, now we will record the whole process of compiling the small v source code, including some problems encountered and solutions.

Download the full source code, with a total of ten compressed packages, and start to decompress the package. After the first decompression, we found that the solution was something that was neither a compressed package nor a file, is it wrong? Or is there a problem during the download and some files are lost? The ghost compressed package is the real source code compressed package. It takes a sigh of relief. This is too professional. People who do not know it cannot beat themselves. Well, unzip the source code and get it.

Then prepare to start compilation. First, build the compilation environment. If the android source code has been synchronized, the tool is ready. If no synchronization is available, download the Eabi tool chain. I have synchronized the source code, Eabi tool chain in the directory: Source directory/prebuilt/linux-x86/inside there are several versions, 4.4.0 the most suitable

Add the path to the environment variable $ gedit ~ /. Bashrc then add export path =$ {path} to the end of the opened file }: /home/foree/cm7-coder/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/binexport arch = arm (used to specify the compilation type as arm, variable assignment see makefile files on the top) $ source ~ /. Bashrc (update the configuration file) and then start to configure the makefile at the top level of the compilation file to specify the compilation type and the path of the compilation tool, such:
As shown in the figure, the environment variable configuration is complete, and then the files and modules to be added for Kernel compilation are configured, as shown in figure

Find the msm7627_blade_defconfig file, and set it to the Kernel configuration file of small V, as shown in the following figure:

Write the configuration file of small V by default. config File (because the default file compiled by make is. config File (hidden file, CTRL + H display visible), this step is written. in the config file, you can directly use make to compile the file) and then make
As shown in, the zimage file is found in the arch/ARM/boot/directory, indicating that the kernel compilation is complete! ========================================================== ======================================== During the compilation process, if you encounter some problems, such as the problem and the steps to solve the problem: PS: (right-click the image and save it as a local image, you can view the full graph) the figure is a little longer...

Add the missing files one by one, and then make and compile the files. PS: I'm complaining. ZTE's staff are also so careless that they have lost so many files that they really have no sense of responsibility!