> From this discussion: > > http://gcc.gnu.org/ml/gcc-patches/2001-05/msg00780.html > > it sounds like only code built with GCC 2.x will refer to __eprintf.Also, the official MinGW gcc-2.95.3 package doesn't include an assert.h, so it seems like MinGW has probably always used its own assert.h, not the version GCC used to provide, so no code built with MinGW would ever have referred to __eprintf. But I'm not 100% sure about this and I can't actually test it. Anyway, I'd vote for removing all references to __eprintf from lib/System/Win32/DynamicLibrary.inc. Thanks, Jay.
Hello, Jay> Also, the official MinGW gcc-2.95.3 package doesn't include an > assert.h, so it seems like MinGW has probably always used its own > assert.h, not the version GCC used to provide, so no code built with > MinGW would ever have referred to __eprintf. But I'm not 100% sure > about this and I can't actually test it.Thanks for tracking, this!> Anyway, I'd vote for removing all references to __eprintf from > lib/System/Win32/DynamicLibrary.inc.Agree. Julien, what do you think? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
On Sat, Apr 18, 2009 at 12:13:55AM +0400, Anton Korobeynikov wrote:> > Anyway, I'd vote for removing all references to __eprintf from > > lib/System/Win32/DynamicLibrary.inc. > Agree. Julien, what do you think?That's fine with me. I'll test it once the change is made. Thanks, Julien -- Julien Lerouge PGP Key Id: 0xB1964A62 PGP Fingerprint: 392D 4BAD DB8B CE7F 4E5F FA3C 62DB 4AA7 B196 4A62 PGP Public Key from: keyserver.pgp.com