[ANNOUNCE] xorg-server

Dan Nicholson dbn.lists at gmail.com
Tue Jun 3 12:03:30 PDT 2008

On Tue, May 27, 2008 at 1:54 PM, Matthieu Herrb <matthieu.herrb at laas.fr> wrote:
> Brian Paul wrote:
>> Donnie Berkholz wrote:
>>> On 12:44 Mon 26 May     , Dan Nicholson wrote:
>>>> On Mon, May 26, 2008 at 12:38 PM, Matthieu Herrb <matthieu.herrb at laas.fr> wrote:
>>>>> Hi,
>>>>> what's the mesa version (or tag from git) to use with this version (and
>>>>> upcoming 1.5)? Apparently 7.0.3 is not recent enough, as it doesn't have
>>>>> the defintion of the __DRIcoreExtension and other things that are
>>>>> referenced in glxdri.c.
>>>> You definitely need master. I think Brian is planning on a mesa-7.1.0
>>>> release real soon.
>>> This brings up a good point, though. Tags are cheap. Could whoever makes
>>> a snapshot release just add a tag to mesa to indicate what git revision
>>> builds with it?
>> Similarly, a tag of the DRM tree would be good.
>> I'm prepping a 7.1 release candidate now (and will make a git tag)...
> Mesa 7.1rc1 doesn't work with xserver
> checking for GL... yes
> Creating destination directories for mesa module ... DONE
> Creating destination directories for glx module ... DONE
> Checking that the source files exist for mesa module ... DONE
> Checking that the source files exist for glx module ...
>    error:   /usr/xenocara/dist/Mesa/src/glx/x11/indirect_dispatch.c not
> found
> configure: error: Failed to link Mesa source tree.  Please specify a
> proper path to Mesa sources, or disable GLX.
> *** Error code 1

I have two commits in the 1.5-glx branch of my xserver repo that allow
1.5 to build against mesa-7.1+. They add the glapi files back into the
xserver tree like has been done on master and check for mesa-7.1+ so
the __DRIcoreExtension is available. However, the mesa source still
needs to be available to build GLcore unless the swrast dri work is
backported from master. The second commit makes the build work again
with the sources in mesa-7.1rc1.


The commits in the above branch are:

I think that's the minimal amount of hackery needed to get things
working. This is all much cleaner on master.


More information about the xorg mailing list