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

[Jeffrey Walton]

On Sat, Jan 9, 2021 at 2:31 PM Paul Eggert <eggert@cs.ucla.edu> 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?

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.

Stop using strstr if it s not used. WTF are you breaking my build for???

Jeff