Re: GNU M4 1.4.15 uses a buggy replacement strstr...

On Sat, Jan 09, 2021 at 02:33:34PM -0500, Jeffrey Walton wrote:
> On Sat, Jan 9, 2021 at 2:31 PM Paul Eggert <[email protected]> wrote:
> >
> > On 1/9/21 11:19 AM, Jeffrey Walton wrote:
> > >> Bison 'configure' can't fix an m4 with a
> > >> buggy strstr, as that's baked into m4. All Bison's 'configure' can do is
> > >> tell you that your m4 is buggy, which is what it's doing.
> > > It should use the updated strstr that is known good. That's what
> > > Gnulib provides.
> >
> > It sounds like I haven't resolved your confusion, then. As I tried to
> > explain, Bison does not use strstr.
> 
> Then why the hell are you breaking my build?


Bison calls M4 to turn its skeletons into files appropriate for direct
compiler input.  Bison's autoconf examines the m4 which bison will be
calling when built, as a prophylactic measure.  That examination reveals
that your M4 contains a bug.  The nature of that bug in M4 is that the
strstr library routine called by m4 is faulty.

Be well,
    -- Jacob