Re: [Mingw-w64-public] there is lib and lib64, how target 32-bit/64-bit?

2014-01-17 Thread Ivan Garramona
You have to use the flags -m32 or -m64 to specify the target. The i686 will target 32bit by default, the same happens with the x86_64, it defaults to 64bit. 2014/1/17 Jim Michaels > there is lib and lib64, how do I target specific cpu type (32-bit/64-bit)? > am using > i686-4.9.0-snapshot-20131

[Mingw-w64-public] there is lib and lib64, how target 32-bit/64-bit?

2014-01-17 Thread Jim Michaels
there is lib and lib64, how do I target specific cpu type (32-bit/64-bit)? am using i686-4.9.0-snapshot-20131119-rev205009-posix-sjlj-rt_v4 x86_64-4.9.0-snapshot-20131119-rev205009-posix-sjlj-rt_v4 which of these compilers is hosted on x64? does posix mean the posix subsystem of windows be insta

Re: [Mingw-w64-public] Linker crash

2014-01-17 Thread Jan Blok
> -- > > Subject: Re: [Mingw-w64-public] Linker crash > To: "mingw-w64-public@lists.sourceforge.net" > > Message-ID: > < > calc40c88ap2_vggkhgwp3dahb6nx-rgkdffhezn+lof16td...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > > > Hi, > > > >

Re: [Mingw-w64-public] Memory leaks in exception handling? The third example(test suites).

2014-01-17 Thread Hannes Domani
lh_mouse schrieb am 15:06 Freitag, 17.Januar 2014: > No std::exception_ptr invoked, still there seems to be memory leaks. > Run make_test.cmd and you will get a.exe. Then run a.exe. > I got the following results: I've tried now your example and came to the same(?) result. These were the leaks I d

[Mingw-w64-public] Memory leaks in exception handling? The third example(test suites).

2014-01-17 Thread lh_mouse
No std::exception_ptr invoked, still there seems to be memory leaks. Run make_test.cmd and you will get a.exe. Then run a.exe. I got the following results: thread 10256: malloc(8) = 00474730 // This leaked. thread 10256: malloc(2) = 00474740 thread thread 10820: malloc(100) = 004749C8 thread

Re: [Mingw-w64-public] (no subject)

2014-01-17 Thread Jim Michaels
the 0XC07B incorrect image error dialog I am geting on startup of my 64-bit program leads me to conclude that: - since crtdll.dll is a 32-bit dll (ms stored 32-bit dll's and exes in c:\windows\SysWOW64 and 64-bit stuff in c:\windows\system32 go figure), - and crtdll.dll is not available in s

Re: [Mingw-w64-public] (no subject)

2014-01-17 Thread Jim Michaels
here is the commandline, -lshell32 has been included. commandlines are exactly the smae for 64-bit and 32-bit except for path to g++.exe so, 32-bit compiler's libshell32.a is missing that function apparently.  d:\i686-4.9.0-snapshot-20131119-rev205009-posix-sjlj-rt_v4\mingw32\bin\g++.exe   

Re: [Mingw-w64-public] GNU Make 4.0

2014-01-17 Thread Alexpux
17 янв. 2014 г., в 13:20, Ruben Van Boxem написал(а): > 2013/12/16 Ruben Van Boxem > 2013/12/16 Alexey Pavlov > 2013/12/16 Ruben Van Boxem : > > 2013/12/16 niXman > >> > >> Ruben Van Boxem 2013-12-16 13:34: > >> > Hi, > >> > > >> > Quick question: does the GNU Make 4.0 release mean I don't ne

Re: [Mingw-w64-public] GNU Make 4.0

2014-01-17 Thread Ruben Van Boxem
2013/12/16 Ruben Van Boxem > 2013/12/16 Alexey Pavlov > >> 2013/12/16 Ruben Van Boxem : >> > 2013/12/16 niXman >> >> >> >> Ruben Van Boxem 2013-12-16 13:34: >> >> > Hi, >> >> > >> >> > Quick question: does the GNU Make 4.0 release mean I don't need to >> >> > patch >> >> > the hell out of GNU M

Re: [Mingw-w64-public] Mingw toolchains and Clang

2014-01-17 Thread Koehne Kai
> -Original Message- > From: Alexey Pavlov [mailto:alex...@gmail.com] > Sent: Wednesday, January 15, 2014 6:36 PM > To: mingw-w64-public@lists.sourceforge.net > Subject: [Mingw-w64-public] Mingw toolchains and Clang > > Long time ago we add possibility to build Clang into mingw-builds scr