Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread JonY
On 4/17/2012 01:21, Ozkan Sezer wrote: > On Mon, Apr 16, 2012 at 7:58 PM, Ruben Van Boxem > wrote: >> Op 16 apr. 2012 18:55 schreef "Ozkan Sezer" het >> volgende: >> >> >>> >>> On Mon, Apr 16, 2012 at 7:22 PM, NightStrike >>> wrote: On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem wr

Re: [Mingw-w64-public] help for a small debug tool on Windows

2012-04-16 Thread Vincent Torri
Hey On Sat, Mar 31, 2012 at 6:58 PM, Vincent Torri wrote: > Hey > > I'm writing a  small tool to do mem leak check, and later GDI leak > checks. That tool, named 'examine', is intended to be used like > valgrind, that is, no linkage (unlike mpatrol, for example). The usage > is : examine my_test_

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread Ozkan Sezer
On Mon, Apr 16, 2012 at 7:58 PM, Ruben Van Boxem wrote: > Op 16 apr. 2012 18:55 schreef "Ozkan Sezer" het > volgende: > > >> >> On Mon, Apr 16, 2012 at 7:22 PM, NightStrike >> wrote: >> > On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem >> > wrote: >> >> 2012/4/16 JonY >> >>> >> >>> On 4/16/2

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread Ruben Van Boxem
Op 16 apr. 2012 18:55 schreef "Ozkan Sezer" het volgende: > > On Mon, Apr 16, 2012 at 7:22 PM, NightStrike wrote: > > On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem > > wrote: > >> 2012/4/16 JonY > >>> > >>> On 4/16/2012 08:48, niXman wrote: > >>> > Hello! > >>> > > >>> > When building gcc -

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread Ozkan Sezer
On Mon, Apr 16, 2012 at 7:22 PM, NightStrike wrote: > On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem > wrote: >> 2012/4/16 JonY >>> >>> On 4/16/2012 08:48, niXman wrote: >>> > Hello! >>> > >>> > When building gcc -> lto-plugin, when linking liblto_plugin.dll I get >>> > the following linker e

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread NightStrike
On Mon, Apr 16, 2012 at 11:59 AM, Ruben Van Boxem wrote: > 2012/4/16 JonY >> >> 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  .

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread Ruben Van Boxem
2012/4/16 JonY > 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/

Re: [Mingw-w64-public] Inconsistencies in C pow() function

2012-04-16 Thread Jonathan Liu
On 15/04/2012 1:41 AM, Kai Tietz wrote: > Hmm, well our implementation interpretes the ISO C99 definition > > "pow (x, y) signals the invalid operation exception for finite x< 0 > and finite non-integer y. Therefore has as result -Nan. Compared values are not the same (powtest.cpp:149) Expecte

Re: [Mingw-w64-public] undefined reference to __ms_vsnprintf

2012-04-16 Thread JonY
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