On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem <[email protected]> wrote: > 2012/4/16 JonY <[email protected]> >> >> On 4/16/2012 08:48, niXman wrote: >> > Hello! >> > >> > When building gcc -> lto-plugin, when linking liblto_plugin.dll I get >> > the following linker error: >> >> >> >> libtool: link: i686-w64-mingw32-gcc -shared .libs/lto-plugin.o \ >> >> -momit-leaf-frame-pointer ../libiberty/libiberty.a \ >> >> -Wl,--stack -Wl,12582912 \ >> >> -o .libs/liblto_plugin-0.dll -Wl,--enable-auto-image-base \ >> >> -Xlinker --out-implib -Xlinker .libs/liblto_plugin.dll.a >> >> Creating library file: >> >> .libs/liblto_plugin.dll.a../libiberty/libiberty.a(simple-object-coff.o):simple-object-coff.c:(.text+0x1c3): >> >> undefined reference to __ms_vsnprintf >> > >> > >> > This error occurs with the mingw-w64-v2.0.2 from svn: >> > https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/tags/v2.0.2/ >> > If I use the trunk version - everything is OK. >> > >> > OS: win7-64 >> > >> > >> >> It was fixed in trunk sometime ago. > > > Yet that doesn't help people using the stable branch...
It just means we have to convince Ozkan to back port it (or at least approve a back port). Perhaps doubling his salary will be enticement enough :) :) ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
