On Mon, Oct 21, 2002 at 08:08:20PM +0200, Benjamin Herrenschmidt wrote: > >[using /usr/include/linux etc symlinks] > >Worked for ages. > > Well, maybe, but it has always been the wrong thing to do, > at least according to Linus, and this have been more of > a problem with recent kernels. Some reasons are userland > abuse of inline function declared in kernel headers, others > are possibly type pollution, and finally, the simple fact > that your glibc headers aren't just supposed to work with > different kernel headers than the ones this glibc was > built with (oh well....)
That's what I thought too. Is there any reason, then, that the install script for the binary dri module releases tries to use /usr/include/linux/... stuff per default? How do I even tell the script where to look for the include files of the running kernel for the drm module build process? For example, I built my current kernel on /home/mcornils/kernel-source-2.4.18, my /usr/src/linux still points to the kernel used to compile my distro's libc, how do I communicate this to the build script? A TREE environment variable didn't work. It did work when changing /usr/include/linux/ to the evil symlinks. Ugly. > If you need access to real up-to-date kernel headers, > you'd rather go look at the symlink in > /lib/modules/kernel_version/build if it exist, or ask > the user (eventually fallback to /usr/src/linux). Maybe this strategy could be used in the build scripts, too? Thanks for the great software otherwise, -Malte #8-) ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576298;k?http://www.sun.com/javavote _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
