Messages in this thread | | | Subject | Re: [PATCH 0/2] kbuild updates | From | Martin Schlemmer <> | Date | Mon, 21 Jun 2004 00:16:02 +0200 |
| |
On Mon, 2004-06-21 at 00:03, Sam Ravnborg wrote: > On Sun, Jun 20, 2004 at 11:30:34PM +0200, Martin Schlemmer wrote: > > > > I know Sam's mta blocks my mail at least (lame isp), but for the rest, > > please reconsider using this. > Hmm, got your mail. > > > Many external modules, libs, etc use > > /lib/modules/`uname -r`/build to locate the _source_, and this will > > break them all. > Examples please. What I have seen so far is modules that was not > adapted to use kbuild when being build. > If they fail to do so they are inherently broken. >
Well, glibc use it for instance as an fall-through if you do not specify it via ./configure arguments, or environment (yes, glibc should not use it, etc, etc, no flames please =). So as well does alsa-driver, nvidia's drivers (gah, puke, yes, its got some binary-only stuff in there ;), ati's drivers and a lot of other stuff (if you really need them all I can try to find time to look for more).
I am not sure about ati's drivers and alsa, but nvidia uses kbuild.
Thanks,
-- Martin Schlemmer [unhandled content-type:application/pgp-signature] | |