> In article <003401c1725a$975ad4e0$f5976dcf@nwfs> you wrote:
> > OK. Cool. Now we are making progress. I think this is a nasty
> > There are numerous RPMs that will build against the kernel tree and be
> > busted. I would expect an rpm -ba on your DEFAULT kernel in Redhat with
> > the sources contained in the kernel.rpm files to also be broken unless
> > someone has done this.
> That's why Red Hat ships the kernel-source RPM; you can build external
> modules against that and it has the "make dep" information for all kernels
> Red Hat ships for that platform (with a smart "if" that selects the
> currently running one)........... But note the word "external". You build
> another directory and don't touch the original .config file or tree......
> Unless you need core changes, that's perfectly possible for almost all
I would anticipate seeing this problem with their kernel source RPM. In
fact, I do,
you have to do a make distclean before you can use it because of the way
script munges all the versioned trees into a tmp area during RPM creation.
one source tree (usually the last one they built) and lots of binary rpm
versions from the
one tree (i.e. i386, i686, etc.).
> Arjan van de Ven
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/