From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
Description of problem:
With the 2.6.x kernel RPMs, it appears that vmlinux has been moved to
the kernel-debuginfo RPM.
Some third party kernel modules require vmlinux in order to build.
During the build process, these modules use modpost, which takes
vmlinux as its first argument. As a result, these modules cannot be
built without installing the kernel-debuginfo package or rebuilding
Not having done any kernel module development, I am assuming that
these modules need to use modpost (and therefore vmlinux) during the
build process. If this is not the case, then could someone let me know
so that I can inform the module developers.
Anyway, since some third party modules require vmlinux to build, it
would seem more sensible to include vmlinux in an RPM other than the
kernel-debuginfo RPM. If a kernel-devel RPM existed, then it would
make sense to include it there. Since no kernel-devel RPM exists, I
think that vmlinuz should be included in the kernel RPM.
One example of modules that require vmlinux are the MADWIFI drivers
available at <http://sourceforge.net/projects/madwifi/>.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(1) Install kernel-2.6.1-1.65.i686.rpm, but do not install
corresponding debuginfo RPM.
(2) Boot using the 2.6.1-1.65 kernel.
(3) Download the MADWIFI drivers from CVS at
(4) Compile the MADWIFI drivers.
Actual Results: MADWIFI compilation fails because it cannot find vmlinux.
Expected Results: I would expect vmlinux to be present.
this needs to be fixed in the madwifi stuf then.
Could you please provide more information?
Do you mean that madwifi is not supposed to be uing modpost?
not by itself for sure