On Sat, Jan 9, 2021 at 2:14 PM Paul Eggert <[email protected]> wrote: > > On 1/9/21 10:31 AM, Jeffrey Walton wrote: > > If you know you need strstr, unconditionally use the one provided by > > Gnulib. That's why Gnulib exists. > > And GNU m4 now does that so the bug has already been fixed. > > It sounds like there's some confusion here. What do you want the Bison > developers to do, exactly?
When Bison thinks there's a buggy strstsr, use the known good provided by Gnulib. Don't waste people's time with it. I won't update Autotools. It is broken beyond repair. Or, based on my experience, Autotools upgrades are broken on Linux, OS X and Solaris. Based on my experience, I can update the entire suite (M4, Autoconf, Automake and Libtool), and the new programs will still use the old shit in /usr. > 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. Jeff
