On Mon, 2006-05-29 at 00:05 -0700, 4Front Technologies wrote:
> Brian F. G. Bidulock wrote:
> > Arjan,
> >
> > On Mon, 29 May 2006, Arjan van de Ven wrote:
> >> external modules shouldn't care, they really really should inherit the
> >> cflags from the kernel's makefiles at which point.. the thing is moot.
> >
> > Yes, and ultimately the kernel's makefile (if present) are the best
> > place to get CFLAGS from. However, the task of ensuring that the
> > correct Makefile is present and that the correct configuration
> > information is feeding it (back to .config) is distribution specific
> > and not always straightforward.
> >
> > --brian
> >
> >
>
>
> How about external modules that have a kernel dependant part and kernel
> independant part?.
tough luck :)
> Kernel independant part could live in a separate tree and
> has its own makefiles.
as long as those makefiles inherit the proper CFLAGs it's no big deal.
If not then you need to glue them together properly, but thankfully the
GPL gives you the freedom to tinker with the sources you get so you can
do that.
> But regparm requires that ALL parts linked into the module need to have regparm
> defined. So it's another headache to write makefiles for the kernel independant
> part to figure out if the distro support regparm or not.
just inherit the cflags. You need to have matching cflags and compiler
anyway for many other reasons; this one is no exception.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
