Messages like the following can be seen which indicate that, the defines are missing and one has to manually change the leading "yy" with the appropriate prefix. Issue covers all three lexers - glsl, glcpp an mesa/program. ./src/compiler/glsl/glsl_lexer.ll: In function ‘void _mesa_glsl_lexer_ctor(_mesa_glsl_parse_state*, const char*)’: ./src/compiler/glsl/glsl_lexer.ll:631:44: error: ‘yylex_init_extra’ was not declared in this scope yy_scan_string(string, state->scanner); ^ ./src/compiler/glsl/glsl_lexer.ll:632:41: error: ‘yy_scan_string’ was not declared in this scope } ^ ./src/compiler/glsl/glsl_lexer.ll: In function ‘void _mesa_glsl_lexer_dtor(_mesa_glsl_parse_state*)’: ./src/compiler/glsl/glsl_lexer.ll:638:32: error: ‘yylex_destroy’ was not declared in this scope } ^
The following should address the issue, although the question stands: are we doing something wrong or this is a flex bug. https://patchwork.freedesktop.org/series/14477/
Is this a blocker for 13? The release won't need flex to compile as it'll be pre-generated for the tarball
(In reply to Mike Lothian from comment #2) > Is this a blocker for 13? The release won't need flex to compile as it'll be > pre-generated for the tarball That's correct. Some distros still do autoreconf + friends which leads (not 100% sure) to those being re-generated. Fwiw this and others are more of "personal favourites". If they're not ready for 13.0.0, there's always 13.0.1 ;-)
Looks like a flex bug: https://github.com/westes/flex/issues/113
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.