thanks for the info, I will look into that.
BTW, I falled back on 6.4, because I have really strange behaviour during the compilation of the 6.4.1 with VisualC++ .Net 2003
I will use 6.4 for my dev, and try also (in parallel) to fix the 6.4.1

From: Karl Schultz []
Sent: Wednesday, December 14, 2005 9:12 AM
To: Stephane Routelous
Subject: Re: [Mesa3d-users] link error on Windows

Start by looking in gl_mangle.h.

These entry points were just added, I think.  gl_mangle.h needs to be regenerated by the shell script embedded at the top of that file.  Or, the script isn't processing these two entry points correctly.

In either case, you can hack around it for the short term by either running the script to regen the file or just by adding the two missing #defines to mangle these function names.

If Brian doesn't get to it before I do, I'll regen gl_mangle.h and update it in CVS to fix it correctly.

mesa.def may also need updating.  Remember that you are probably using a modified version of mesa.def to account for the mangle, as discussed in README.WIN32.

On 12/14/05, Stephane Routelous <> wrote:
[Mesa cvs from 14 dec 2005 - VisualC++ 6.0 and Visual C++ .Net 2003 on WindowsXP SP2]
when compiling Mesa6.4.1 (CVS from yesterday) on Windows , and defining USE_MGL_NAMESPACE, I have the following link errors :
mesa.lib(glapi.obj) : error LNK2001: unresolved external symbol _glGetQueryObjectui64vEXT@12
mesa.lib(glapi.obj) : error LNK2001: unresolved external symbol _glGetQueryObjecti64vEXT@12
What should I change to make mesa compile ?