search for: msg00780

...true fi Debian's mingw32 package is built with host != target, and without the --with-sysroot and --with-headers options. So this logic kicks in, and prevents __eprintf from being built in libgcc.a, since it calls into libc. >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. Thanks, Jay.

Hello, Jay > but I don't understand what they are for. Do they let lli execute > programs in which the compiler has hard-coded calls to __eprintf? Does > that mean that __eprintf ought to be found in libgcc? Yes. And I believe it was there, at least for "official mingw gcc", which is 3.4.5. Could you please investigate why you don't have this in your libgcc? Is it

> 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...