[Mesa-dev] undefined C++ GLSL symbol error

Kenneth Graunke kenneth at whitecape.org
Tue Jan 31 19:44:34 PST 2012


On 01/31/2012 06:26 PM, Matt Turner wrote:
> On Tue, Jan 31, 2012 at 8:32 PM, Brian Paul<brianp at vmware.com>  wrote:
>> On 01/31/2012 02:44 PM, Zack Rusin wrote:
>>>
>>> On Tuesday, January 31, 2012 12:02:28 PM Matt Turner wrote:
>>>>>
>>>>> $ make>log
>>>>> ar: creating libglapi.a
>>>>> ar: creating libmesa.a
>>>>> ar: libmesa.a: Error reading ../../src/glsl/.libs/: Is a directory
>>>>> ar: creating libmesagallium.a
>>>>> ar: libmesagallium.a: Error reading ../../src/glsl/.libs/: Is a
>>>>> directory
>>>>> ar: creating libegl_glx.a
>>>>> ar: creating libgallium.a
>>>
>>>
>>> Getting similar error, but my build doesn't finish:
>>>
>>> $ make realclean
>>> $ git clean -fxd
>>> $ ./autogen.sh --with-gallium-drivers=svga -with-dri-drivers= --enable-xa
>>> $ make
>>>   ar: creating libmesa.a
>>>   ar: ../../src/glsl/.libs/: File format not recognized
>>>   ranlib: 'libmesa.a': No such file
>>>   ar: creating libmesagallium.a
>>>   ar: ../../src/glsl/.libs/: File format not recognized
>>>   ranlib: 'libmesagallium.a': No such file
>>> ...
>>>   make[3]: *** No rule to make target
>>> '../../../../src/mesa/libmesagallium.a',
>>> needed by 'vmwgfx_dri.so'.Stop.
>>>   make[3]: Leaving directory
>>> '/home/zack/src/mesa/gallium/targets/dri-vmwgfx'
>>>
>>>> I'll keep looking.
>>>
>>>
>>> Could you maybe revert all of this and do it in a branch where we could
>>> iron
>>> out those issues?
>>
>>
>> Yeah, I was thinking the same thing.
>>
>> When we get things working again let's do all follow-on autoconf work on a
>> branch where we can test first.
>>
>> -Brian
>
> I'm okay with that if people will actually test.
>
> The glsl patch has been on the mailing list since September, through
> multiple iterations, and I think only got testing from two other
> people.
>
> I'll revert the glsl stuff tonight.
>
> I think automaking src/mesa/drivers/dri/* is okay, more or less?
>
> Matt

I think trying to revert everything will just make things worse.  I'm 
okay with reverting the very latest bits for now.


More information about the mesa-dev mailing list