Just a guess, but I'd say the 'xargs' command (which is what is throwing the error) is coming from the slackbuild and not from Mesa itself. Does Mesa build if you don't use the slackbuild?
Adam
I'm getting the following mesa compile error:Any help?Code:/bin/ginstall -c -d /tmp/SBo/package-mesa/usr/include/GL /bin/ginstall -c -d /tmp/SBo/package-mesa/usr/lib64 /bin/ginstall -c -d /tmp/SBo/package-mesa/usr/lib64/pkgconfig /bin/ginstall -c -m 644 ../../../include/GL/glut.h /tmp/SBo/package-mesa/usr/include/GL /bin/sh ../../../bin/minstall ../../../lib64/libglut.*so* /tmp/SBo/package-mesa/usr/lib64 /bin/ginstall -c -m 644 glut.pc /tmp/SBo/package-mesa/usr/lib64/pkgconfig gmake[2]: Leaving directory `/tmp/SBo/mesa/src/glut/glx' make[1]: Leaving directory `/tmp/SBo/mesa/src' make[1]: Entering directory `/tmp/SBo/mesa/progs' make[1]: Nothing to be done for `install'. make[1]: Leaving directory `/tmp/SBo/mesa/progs' make: Nothing to be done for `default'. xargs: str: No such file or directory
Just a guess, but I'd say the 'xargs' command (which is what is throwing the error) is coming from the slackbuild and not from Mesa itself. Does Mesa build if you don't use the slackbuild?
Adam
Thanks for response.
This is same slackbuild I've used for last 9-12 months. It always worked fine before. I could post if its helpful. But you may be right. I just watched it and it looks like it makes it almost to completion before kicking out.
Nevermind.
Somehow a page-return got installed so that xargs strip looked like xargs str. Not sure how this could have happened though as I have a batch file that calls the slackbuild. The only change I make to the slackbuild is the version number. Oh well. Thanks.