On Mon, Nov 11, 2013 at 7:58 AM, Brian Paul <bri...@vmware.com> wrote: > On 11/08/2013 11:49 AM, Eric Anholt wrote: >> >> Jose Fonseca <jfons...@vmware.com> writes: >> >>> This change seems makes dri3proto a hard requirement to build with >>> automake. Is that strictly necessary? I tried to find ubuntu >>> packages for it to install on my build slave, but it doesn't seem they >>> exist yet. >> >> >> Well, we could build more build infrastructure for not building it, but >> there are released tarballs and it's a tiny little set of headers. > > > Since DRI3 depends on several new packages which aren't readily available > yet (yum, apt-get, etc), I'm really glad to have the --disable-dri3 option > (Thanks, Armin). > > I've tried building the libxshmfence-1.0 package on two different systems > now and both failed: > > $ ./configure --prefix=/usr/local > seems to work > > $ make > [...] > /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 > -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT xshmfence.lo -MD -MP -MF > .deps/xshmfence.Tpo -c -o xshmfence.lo xshmfence.c > ../libtool: line 831: X--tag=CC: command not found > ../libtool: line 864: libtool: ignoring unknown tag : command not found > ../libtool: line 831: X--mode=compile: command not found > ../libtool: line 997: *** Warning: inferring the mode of operation is > deprecated.: command not found > ../libtool: line 998: *** Future versions of Libtool will require > --mode=MODE be specified.: command not found > ../libtool: line 1141: Xgcc: command not found > ../libtool: line 1141: X-std=gnu99: command not found > ../libtool: line 1141: X-DHAVE_CONFIG_H: command not found > ../libtool: line 1141: X-I.: command not found > ../libtool: line 1141: X-I..: command not found > ../libtool: line 1141: X-g: command not found > ../libtool: line 1141: X-O2: command not found > ../libtool: line 1141: X-MT: command not found > ../libtool: line 1141: Xxshmfence.lo: command not found > ../libtool: line 1141: X-MD: command not found > ../libtool: line 1141: X-MP: command not found > ../libtool: line 1141: X-MF: command not found > ../libtool: line 1141: X.deps/xshmfence.Tpo: No such file or directory > ../libtool: line 1141: X-c: command not found > ../libtool: line 1192: Xxshmfence.lo: command not found > ../libtool: line 1197: libtool: compile: cannot determine name of library > object from `': command not found > make[2]: *** [xshmfence.lo] Error 1 > > > -Brian
I saw this too. I think it's some kind of packaging failure (autotools versions much too old on Keith's system?). I was able to work around it by running autogen.sh to regenerate the scripts. :( _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev