You're correct Philippe, after symlinking the 2.6.28-11-generic autoconf.h file from /usr/src/linux-headers-2.6.28-11-generic/include/linux/autoconf.h to /usr/src/linux-headers-`uname -r`/include/linux/autoconf.h it was then created in /lib/modules/`uname -r`/build/include/linux/autoconf.h I will have to make appeal to the Ubuntu developers. Currently, I am frustrated to no end with this, but I thank you for your prompt responses. Stephen Pinker ----- Original Message ---- From: Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx> To: S Pinker <stephenpinker79@xxxxxxxxx> Cc: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> Sent: Friday, August 14, 2009 11:02:23 PM Subject: Re: Ubuntu autoconf.h The problem is not the single autoconf.h file. All the Linux kernel headers required to rebuild any Linux driver from source code are expected to be accessible from /lib/modules/`uname -r`/build/include or /lib/modules/`uname -r`/build being a symbolic link to the actual kernel code which includes the include/ directory. All this work is usually performed by the kernel-devel package in any distribution (but Ubuntu ???) - http://vouters.dyndns.org:8080/ Philippe Vouters (Fontainebleau/France)
