t...@gmplib.org (Torbjörn Granlund) writes:
> It is not completely obvious to me that one can link things together
> where some parts want to compliant stdio and some other parts want a
> non-compliant stdio.
I don't really know how that magic works, but my guess guess is that
it's per
ni...@lysator.liu.se (Niels Möller) writes:
#if defined(__WIN32__) && define (__GNUC__)
#define __USE_MINGW_ANSI_STDIO 1
#endif
I'd guess there are plenty of windows programs that depend on the
non-standard behavior. So bug-compatibility makes some sense. But we
don't want it.
Claude Heiland-Allen writes:
> Could the macro __USE_MINGW_ANSI_STDIO be relevant?
Yes, perfect! I did
CPPFLAGS=-D__USE_MINGW_ANSI_STDIO ./configure
--host=x86_64-w64-mingw32 --prefix=$HOME/win64
CPPFLAGS=-D__USE_MINGW_ANSI_STDIO make -j 8
Hi Marc,
On 31/03/17 00:27, Marc Glisse wrote:
> On Thu, 30 Mar 2017, Vincent Lefevre wrote:
>
>> On 2017-03-30 10:52:33 +0100, Claude Heiland-Allen wrote:
>>> The failing source code is:
>>>
>>> /* EOF for no matching */
>>> {
>>> char buf[128];
>>> ret = gmp_sscanf (" ", "%s",
On Thu, 30 Mar 2017, Vincent Lefevre wrote:
On 2017-03-30 10:52:33 +0100, Claude Heiland-Allen wrote:
The failing source code is:
/* EOF for no matching */
{
char buf[128];
ret = gmp_sscanf (" ", "%s", buf);
ASSERT_ALWAYS (ret == EOF);
ret = fromstring_gmp_fscanf (" ",
On 2017-03-30 10:52:33 +0100, Claude Heiland-Allen wrote:
> The failing source code is:
>
> /* EOF for no matching */
> {
> char buf[128];
> ret = gmp_sscanf (" ", "%s", buf);
> ASSERT_ALWAYS (ret == EOF);
> ret = fromstring_gmp_fscanf (" ", "%s", buf);
> ASSERT_ALWAYS
On 30/03/17 14:12, Torbjörn Granlund wrote:
> It is not realistic for us to work on this problem as there are
> countless of things which might be wrong.
Good point. I don't think my project in question that uses GMP needs
those functions anyway, so I'll leave it uninvestigated.
Thanks for the