----- Original Message ----- > On Tue, Jan 31, 2012 at 8:32 PM, Brian Paul <bri...@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 wonder if people have use any tools to facility applying patches posted to mesa, as for me locate, save, and applying them takes a lot of time, and more often than not fails due to white space munging. I barely can keep up with the review requests anyway. Matt, if you commit your changes to a branch on fdo, then I can easily test. I can also also setup an automated build job on it and report failures to you. Jose _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev