2013/8/8 LRN <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 07.08.2013 22:37, Michael Cronenworth wrote: >> On 08/07/2013 01:35 PM, LRN wrote: >>> What does "might" mean there? Like, you may get a dependency, or you may >>> not? It doesn't sound like you ALWAYS get a dependency. >>> Previously you WOULD get the dependency if you had code that required >>> it, and WOULD NOT get it otherwise. >>> Now you get it regardless. >>> Note that in #57120 the reporter explicitly does long long division, so >>> for him libgcc is mandatory, and it's fine. >>> For an empty dll - not so much... >> >> Feel free to file a bug for an enhancement. I'm not a MinGW-w64 developer. >> Arguing with me is like arguing with the wind. :) > > After jon_y gave me some tips, i was able to confirm that dependency in > question is pulled by libmingwex. > > After further investigation i was able to fix this problem with the > following patch to mingw-w64-crt. > It removes the use of libmingwex mingw_*printf functions in libmingw32. > These were the functions that pulled libgcc with them. > (just to be safe i've removed both matherr and pseudo-reloc occurrences, > although i suspect that only pseudo-reloc actively contributed to the > problem in my case). >
Thanks for the patch. Please go ahead and apply it. Kai ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
