<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 12-03-14 10:20 AM, Brian Paul wrote: <blockquote cite="mid:CAEUUzO_sYGYQwN-QYYbqiX4NdBET3h8e+Ao3cPxq+ggN84TGAg@mail.gmail.com" type="cite"> <pre wrap="">On Tue, Mar 13, 2012 at 9:14 PM, Matt Turner <a class="moz-txt-link-rfc2396E" href="mailto:mattst88@gmail.com"><mattst88@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Fixes: <a class="moz-txt-link-freetext" href="https://bugs.freedesktop.org/show_bug.cgi?id=47248">https://bugs.freedesktop.org/show_bug.cgi?id=47248</a> Signed-off-by: Matt Turner <a class="moz-txt-link-rfc2396E" href="mailto:mattst88@gmail.com"><mattst88@gmail.com></a> ---  configure.ac |    3 +++  1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index a2d906a..e7994b0 100644 --- a/configure.ac +++ b/configure.ac @@ -66,6 +66,9 @@ if test ! -f "$srcdir/src/glsl/glcpp/glcpp-parse.y"; then     fi  fi  AC_PROG_LEX +if test "x$LEX" != xflex; then +    AC_MSG_ERROR([flex not found - unable to compile glcpp-lex.l]) +fi </pre> </blockquote> <pre wrap=""> What if the system actually has lex? Would that work? Do our .l files use any flex-specific features? -Brian </pre> </blockquote> There has been a similar discussion on xorg-devel when a developer wished to use bison specific features. The BSD systems such as FreeBSD or MAC use the base O/S without additional packages (that they call "ports"). The base OS does not  include GNU versions of lex & yacc. In the light of this discussion I rephrased the xorg wiki for the lex & yacc tools requirements. I suppose mesa is targeting most if not all platforms that xorg builds on. Here it goes: <ul> <li> <a class="http" href="http://en.wikipedia.org/wiki/Yacc">yacc</a> <tt> </tt> The original AT&T parser generator or an upward compatible version such as <a class="http" href="http://www.gnu.org/software/bison/">bison</a> or <a class="http" href="http://invisible-island.net/byacc/">byacc</a> whitout using its specific features </li> <li> <a class="http" href="http://en.wikipedia.org/wiki/Lex_%28software%29">lex</a> <tt> </tt> The original AT&T lexical analyser generator or an upward compatible version such as <a class="http" href="http://flex.sourceforge.net/">flex</a> whitout using its specific features </li> </ul> <a class="moz-txt-link-freetext" href="http://www.x.org/wiki/ModularDevelopersGuide#Required_Tools">http://www.x.org/wiki/ModularDevelopersGuide#Required_Tools</a> In the case where mesa, for the moment, is limited to flex, would there be  a scenario where a builder configures the module such that the glcpp subdir is not build? If so, the configuration should not abort. When building from a tarball which includes the flex generated code, the configuration should not abort if flex is missing as it is not required to have a successful build. This will allow all those systems without flex to build from a tarball.   </body> </html>