On 7/31/2013 19:49, Corinna Vinschen wrote: > On Jul 31 19:31, JonY wrote: >> On 7/31/2013 18:47, Corinna Vinschen wrote: >>> Erm... hang on. On second thought, I'm not sure that this is a bug. >>> The actual bug here was clearly in the Cygwin utils Makefile. >>> >>> In fact, since w32api should only be used by Cygwin executables, why >>> should w32api provide libmingwex.a at all? Linking a Cygwin executable >>> against libmingwex doesn't sound like the right thing to do. Shouldn't >>> rather libmingwex.a just go from w32api? >>> > > I just realize that libmingw*.a is not packed with w32api-runtime > anyway, so my question doesn't make sense. > >> Can you see what happens if libmingwex.a was replaced by the empty libm.a? > > I don't understand what you mean. Can you rephrase the question? >
Sorry, I was confused, I now see user was using the cross compiler, not native gcc. >> It is only _get_output_format require stuff from msvcrt, >> _set_invalid_parameter_handler just uses some typedef declaration. >> >> I'm starting to wonder if this require a deeper fix. > > Not sure, but the problem here was clearly that the crt2.o from > mingw-crt didn't match with what is provided by w32api-runtime. > However, there's no point linking against mingw-crt crt2.o but then use > the libs from w32api, so this isn't really a problem in w32api-runtime. > > So, bottom line is, I'm not sure there's anything to fix in > w32api-runtime at all. > Nope, not related after all. I'm still trying to figure out the error.
signature.asc
Description: OpenPGP digital signature
