Sorry I broke the DRI build, now I see what the problem is. When the Mesa is included in the DRI tree is it is using the DRM driver in the DRI tree. I didn't know that the DRI build would alter the Mesa include paths.
So there are two choices: 1) Copy my changes from Mesa back into the DRI tree. The current set of changes does nothing except remove the redundant h files. It was preparation for later changes. 2) Alter the include path to use the DRM copy in the Mesa tree. Which do we want to do? I have pile of changes ready that require simultaneous changes in mesa and the drm driver. For me it would be much simpler to have the DRM driver and mesa in the same tree. I'm targeting this work to go into xserver, not xfree. But other people want to keep the DRM in the DRI tree. Doing this means I have to be careful about doing parallel check-ins to both trees. It also forces me to work in the DRI tree, a tree that I'm not using. ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
