charlieb-atrpms-devel at budge
Apr 2, 2005, 2:12 AM
Post #6 of 7
(102 views)
Permalink
|
On Sat, 2 Apr 2005, Axel Thimm wrote:
> On Fri, Apr 01, 2005 at 05:40:03PM -0500, Charlie Brady wrote:
> > > As long as there is no proper way to build custom kernel rpms and have
> > > configured and preped kernel sources for each custom kernel, the
> > > macros are useless for 75% of all kmdl projects.
> >
> > How can I help to make what is required generally available? I know that
> > RedHat have made it increasingly difficult to build add-on modules (I have
> > no idea why!), but is it really impossible?
>
> No, otherwise ATrpms wouldn't have any kmdl :)
>
> Take the kernel source from RH, for RHEL3 there should still be
> kernel-source (I hope ...).
Yep (at least as distributed by CentOS).
> Clean up the sources (mrporper), place the
> .config file of your (custom?) kernel into the sources, make
> oldconfig twice, then make depend.
>
> E.g. duplicate all steps required for building the kernel, but don't
> do the build itself (doesn't hurt other than loosing CPU cycles).
Except for the problem that it won't work if you are non-root. And of
course you should be non-root when building RPMs.
And except for the problem that you dirty the source which you've
installed from RPM.
No, not an acceptable solution (I'm not blaming you).
I don't consider Matt Domsch's DKMS acceptable either.
> > I've followed a few threads in archives - but there is a lot of reading to
> > do there. What's their reason for not providing all variants of configs
> > and mangled symbols (in one package or other)?
>
> Stubborness?
Perhaps, but it's not a complete explanation. Doesn't explain changing
something which sort of worked into something that doesn't work at all.
> The kernel maintainer has been swaped since and the
> current one is more open to these issues, so not all hope is lost ...
Where do we talk to him/her?
Alternatively, perhaps we could show them how it should be done (and in
doing so, solve our problem ourselves). Could we not build one package
containing all the config files and mangled symbols headers (I vaguely
remember someone doing that), and have that as a BuildRequires package for
all the kmdl modules?
Thanks
---
Charlie
|
