Matthew Burgess wrote:
> On a very new system (linux-2.6.33 + libdrm-2.4.18) I see the same
> thing. Looking at the README in the tarball for libdrm:
>
> "New functionality in the kernel DRM drivers typically requires a new
> libdrm, but a new libdrm will always work with an older kernel."
>
> As such, I think the right thing to do in this scenario is to just let
> libdrm overwrite the headers it wants to install.
That sounds right to me. The library contains the actual code
that is going to be called by the application, and it sets the
standard for how to do the calls, so as it provides the actual
API, it should set the include headers.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
