Re: GDB 7.99.91 MinGW compilation error in cli-script.c

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 13 May 2017 23:19:06 -0400
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Cc: gdb-patches@sourceware.org
> 
> > How best to solve this?  I worked around by providing my own
> > implementation based on std::ostringstream, but I'm not sure this is
> > TRT.  An alternative would be to use some less problematic API, since
> > currently cli-script.c is the only user of this method, and its needs
> > are quite modest.  And if we do provide a replacement for to_string,
> > should the configure script probe for it, or should we condition it
> > specifically on MinGW and _GLIBCXX_HAVE_BROKEN_VSWPRINTF?
> > 
> > Thoughts?
> 
> I think the best solution would be a check at configure time.  I think 
> it's a function that can be quite handy, so it would be unfortunate if 
> we had to avoid using it, especially if it's easy to implement ourselves 
> for MinGW.  A configure check would be more robust than checking for 
> MinGW or _GLIBCXX_HAVE_BROKEN_VSWPRINTF specifically, in case another 
> platform needs the replacement too, or if the define changes at some 
> point.

I've meanwhile learned that the latest release 5.0 of MinGW runtime
solves this problem.