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

[Paul Eggert]

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. And even if Bison 'configure' 
substituted a working strstr for Bison's own use (which would make no 
sense since Bison does not use strstr), this cannot fix any instances of 
the strstr bug in other packages, such as in GNU m4. You need to arrange 
for the Bison build procedure to use a working m4. That is something you 
can easily do on Solaris; I've done it myself.

If you are still puzzled about the situation, please suggest a specific 
fix to Bison. I suggest emailing us a patch in 'git format-patch' 
format. If you try to do that, you'll find that what you're suggesting 
is impossible, without extreme measures (such as Bison tarballs 
containing complete copies of GNU Autoconf and of GNU m4 source code) 
which we're not gonna do.