In your mail you use the following to build:

make menuconfig ARCH=arm CROSS_COMPILE=arm-eabi-

To build the kernel don't include menuconfig so it should be like this:

make ARCH=arm CROSS_COMPILE=arm-eabi-

or

make menuconfig ARCH=arm CROSS_COMPILE=arm-eabi- uImage
make menuconfig ARCH=arm CROSS_COMPILE=arm-eabi- modules

To change the kernel config use this:

make ARCH=arm menuconfig


On Fri, Apr 15, 2011 at 6:30 AM, Dark Knight <vaisakhru...@gmail.com> wrote:

> Hi Sowmya,
>
> Have to tried checking the available branches in repository?? Clone
> the entire repository and then issue a GIT BRANCH -a command and see
> the available branches and then checkout the correspoding one
>
> On Apr 14, 5:33 pm, sowmya l s <svsp.ram...@gmail.com> wrote:
> > Hi,
> >    I tried to do the following using repo command to get the android-
> > kernel2.6.32, i got the following error:
> >       error: revision android-2.6.32 in kernel/common not found
> >     then how to get android kernel of particular version2.6.32.
> >
> >     Even i tried using git,
> >
> >    git checkout --track -b android-2.6.32 origin/archive/
> > android-2.6.32,
> >
> >    But i felt lots of file missing, ex include/linux/version.h,I was
> > not able to do the following also:
> >
> >     make menuconfig ARCH=arm CROSS_COMPILE=arm-eabi-
> >
> >     scripts/Makefile.build:44: /media/4C90A08B90A07D58/
> > LinuxWorkstation/Project/android-kernel_2.6.32/scripts/basic/Makefile:
> > No such file or directory
> >     make[1]: *** No rule to make target `/media/4C90A08B90A07D58/
> > LinuxWorkstation/Project/android-kernel_2.6.32/scripts/basic/
> > Makefile'.  Stop.
> >
> >     make: *** [scripts_basic] Error 2
> >
> >    Can anyone help me out how to get the android-kernel2.6.32 source
> > code.
> >
> > Regards,
> > Sowmya
>
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
>

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel

Reply via email to