I believe this just means that it was NOT able to build the 'ipt_ecn' module ('iptables' module which is typically used as a filtering, network traffic sniffer/shaper..and many other things. Thats out of topic for this). And thats fine with me. What has got me concerned is, since it apparently failed in the middle, it may have missed out on any book-keeping task(s) which it does at the end of 'make modules'?

Nonetheless, I ran a

Code:

make modules

and it seemed to have went fine (note that ive already installed the modules under /lib/modules/ by doing a

Code:

make modules_install

at the top of the vanilla kernel source tree). I then cd into the directory where my kernel module source code is located. My Makefile in it looks like this:

Code:

obj−m += hello−1.o

all:
make -C /lib/modules/2.6.32.59/build M=$(shell pwd) modules

clean:
make -C /lib/modules/2.6.32.59/build M=$(shell pwd) clean

I DID NOT use the /lib/modules/`uname -r`/build path as I do not want to have these modules linked against the currently running kernel. I will only do an 'insmod' after having booted into the '2.6.32.59' vanilla kernel later. So am I allowed to build a kernel module against a kernel which is not currently running?

Anyways, I try doing exactly that, by doing a

Code:

make all

in the directory where I have my kernel module source. However I get the following errors:

After searching a lot over the internet, ive come across many different opinions but I couldn't figure out a single reason as to why it fails to find the autoconf.h or auto.conf files. These files are present under the source tree