The kernel-devel package seems to include two autoconf.h files, one with content and one with 0 bytes: $ rpm -qvlp kernel-devel-3.3.0-0.rc3.git5.1.fc17.x86_64.rpm | grep autoconf -rw-r--r-- 1 root root 826381 Feb 14 2012 /usr/src/kernels/3.3.0-0.rc3.git5.1.fc17.x86_64/include/generated/autoconf.h -rw-r--r-- 1 root root 0 Feb 14 2012 /usr/src/kernels/3.3.0-0.rc3.git5.1.fc17.x86_64/include/linux/autoconf.h I wonder if this is intentional and if so, what the purpose is.
This is probably coming from a section in the kernel.spec file that does: # Make sure the Makefile and version.h have a matching timestamp so that # external modules can be built touch -r $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/Makefile $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include/linux/version.h touch -r $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/.config $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include/linux/autoconf.h That pre-dates our git usage and I'm not even sure it's needed any longer.
This was fixed in F18.
Cool. How does it end up getting to EL? It's needed there also.
(In reply to comment #3) > Cool. How does it end up getting to EL? It's needed there also. You will need to open a bug against the relevant RHEL release(s) to have it fixed in RHEL. The Fedora and RHEL kernels are maintained separately.
~sigh~ To which I suppose I will get the standard "talk to your EL support sales person" boilerplate and since I don't have one of those, nothing will happen.