I am trying to compile a linux arm kernel on a PC running SUSE Linux. I want to be careful not to disturb anything with the SUSE Linux kernel. This is the make command I execute and the result I get:

> make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/basic/hash
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/arm/Kconfig
***
*** You have not yet configured your kernel!
*** (missing kernel config file ".config")
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
>



Any comments?

It does suggest running "make menuconfig", which is a big tip about what to do before running "make" by itself.

Personally, I'd just download and use buildroot, which works just fine under SuSE 11.x once you install make, flex, subversion and a bunch of development tools that the process requires.

Basically a manner of running
make xxxx_defconfig
make

where xxxx is your board

http://www.at91.com/linux4sam/bin/view/ ... /BuildRoot
http://www.at91.com/linux4sam/bin/view/ ... _buildroot

[quote="CptTitanic"]It does suggest running "make menuconfig", which is a big tip about what to do before running "make" by itself.

Personally, I'd just download and use buildroot, which works just fine under SuSE 11.x once you install make, flex, subversion and a bunch of development tools that the process requires.[/quote]

I just wanted to make sure none of what I did would interfere or contaminate the currently running Linux kernel. I didn't think 'make' would, but I wasn't sure about doing anything else.