search

paul-j-lucas / cdecl

Composing and deciphering C (or C++) declarations or casts, aka ‘‘gibberish.’’
GNU General Public License v3.0
90 stars 11 forks source link

Autoconf: `AC_PROG_LEX` warnings in 2.70 #9

Closed jgottula closed 1 year ago

jgottula commented 3 years ago

Building this project with autoconf 2.70 gives the following warning:

configure.ac:31: warning: AC_PROG_LEX without either yywrap or noyywrap is obsolete
./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from...
./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from...
aclocal.m4:650: AM_PROG_LEX is expanded from...
m4/ax_prog_flex.m4:47: AX_PROG_FLEX is expanded from...
configure.ac:31: the top level

It appears that AC_PROG_LEX was updated in 2.70 to take a somewhat-required-ish parameter: https://www.gnu.org/software/autoconf/manual/autoconf-2.70/html_node/Particular-Programs.html#index-AC_005fPROG_005fLEX-1

And it seems that AX_PROG_FLEX uses AC_PROG_LEX via AM_PROG_LEX; and ax_prog_flex.m4 hasn't yet been updated to deal with the new AC_PROG_LEX parameter.

Don't necessarily know whether there's a lot to do right now, since ax_prog_flex.m4 upstream is still using the legacy syntax. But in any case, it's something to be aware of, I suppose.

paul-j-lucas commented 3 years ago

For now, I'll just wait. Maybe they'll fix it. Short of writing my own macro, there's not much I can do. Also, the docs don't say how backward compatible adding an argument would be to older autoconf.

paul-j-lucas commented 1 year ago

Waiting didn't work since there's no upstream fix. I've instead worked around the issue with f02a78657afb6ddbeb9e66c8becfacad6ad9dea1.