Re: [Mingw-w64-public] Is there a way to confirm just what target gcc.exe (tdm64-1) optimizes for?

2012-09-23 Thread Antony Riakiotakis
gcc -v ? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobi

Re: [Mingw-w64-public] Target optimization specificity

2012-09-23 Thread John E. / TDM
On 9/23/2012 6:48 PM, Richard Haney wrote: *Lots of things regarding GCC's target architecture & optimizations* Hi Richard, You'll have to look at the build log for GSL to determine whether your CFLAGS are being propagated correctly. You can generally expect MSYS to report "i686" for uname

[Mingw-w64-public] Is there a way to confirm just what target gcc.exe (tdm64-1) optimizes for?

2012-09-23 Thread Richard Haney
How can I determine specifically what processor target gcc (tdm64-1) optimizes for? That's specifically gcc (tdm64-1) versionĀ 4.6.1 I'm concerned about in my case. -- Live Security Virtual Conference Exclusive live event

[Mingw-w64-public] Target optimization specificity

2012-09-23 Thread Richard Haney
I did a build of gsl-1.15 using gcc.exe (tdm64-1) 4.6.1 under MSYS, and I used the following command line for configure: ./configure CFLAGS="-g -O2 -march=native -fexceptions" --prefix=/c/gsl-1.15_64_-g_O2 &> gsl-1.15_configure.out I was hoping that gcc would recognize my Intel Core i5-2410M Pro

Re: [Mingw-w64-public] libuv build fail with 32bit rubenvb 4.7.1

2012-09-23 Thread Jon
> > fyi...the following libuv build fail still exists in > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z` > > > > Yes, that's to be expected. There was no new tagged MinGW-w64 release. The > previous easy fix still applies. > > Ruben Yes, using tagged vs. non-tagged is an interesting ca

Re: [Mingw-w64-public] libuv build fail with 32bit rubenvb 4.7.1

2012-09-23 Thread Ruben Van Boxem
2012/9/23 Jon > fyi...the following libuv build fail still exists in > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z` > Yes, that's to be expected. There was no new tagged MinGW-w64 release. The previous easy fix still applies. Ruben > > > > On 9/11/12, Jon wrote: > > > In an custom m

Re: [Mingw-w64-public] libuv build fail with 32bit rubenvb 4.7.1

2012-09-23 Thread Jon
fyi...the following libuv build fail still exists in `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z` > On 9/11/12, Jon wrote: > > In an custom msys wrapped > > `i686-w64-mingw32-gcc-4.7.1-2-release-win32_rubenvb.7z` toolchain I get the > > following build fail with libuv that doesn't occu

Re: [Mingw-w64-public] rubenvb-4.7.1-2-release: ld.exe crashes on XP

2012-09-23 Thread Ruben Van Boxem
2012/9/23 Luis Lavena > On Wed, Sep 19, 2012 at 11:41 PM, Hiroshi Shirosaki wrote: > > > > Hi, > > > > ld of binutils 2.23.51.20120816 crashed. > > > > But with latest source of binutils, this issue seems to be solved. > > Build has succeeded with the following version. > > > > sh-3.1$ ld -V > >

Re: [Mingw-w64-public] rubenvb-4.7.1-2-release: ld.exe crashes on XP

2012-09-23 Thread Luis Lavena
On Wed, Sep 19, 2012 at 11:41 PM, Hiroshi Shirosaki wrote: > > Hi, > > ld of binutils 2.23.51.20120816 crashed. > > But with latest source of binutils, this issue seems to be solved. > Build has succeeded with the following version. > > sh-3.1$ ld -V > GNU ld (rubenvb-4.7.1) 2.23.51.20120919 > Su

Re: [Mingw-w64-public] i686-w64-mingw32-gcc dependency problem (GLIBC_2.14)

2012-09-23 Thread KC
On Sun, Sep 23, 2012 at 5:57 PM, JonY wrote: > On 9/23/2012 17:49, KC wrote: > > Hi > > > > I use mingw-w64 WIN64 cross compiler for quite a while under CentOS 6.x > > which use glibc-2.12. > > (I use this version: mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2) > > and everything is OK. > > > >

Re: [Mingw-w64-public] GCC 4.7.2 rubenvb build

2012-09-23 Thread Loaden
Which version of GDB? trunk branch or final release? You can try to use the same version of GDB with MinGW-Builds. In many times, it should be GDB-self problem. 2012/9/23 Ruben Van Boxem > The gdb slow startup issue for Qt programs is still under investigation. -- *Please don't ask where I c

[Mingw-w64-public] GCC 4.7.2 rubenvb build

2012-09-23 Thread Ruben Van Boxem
Hi everyone, I am in the process of uploading GCC 4.7.2 with MinGW-w64 v2.0.6. I have fixed the mingw32-make issue (by applying the patch I previously forgot to apply), so now Qt5' configure and other stuff that didn't, will now succeed. I also added the "envsetup" directory to the source packag

Re: [Mingw-w64-public] i686-w64-mingw32-gcc dependency problem (GLIBC_2.14)

2012-09-23 Thread JonY
On 9/23/2012 17:49, KC wrote: > Hi > > I use mingw-w64 WIN64 cross compiler for quite a while under CentOS 6.x > which use glibc-2.12. > (I use this version: mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2) > and everything is OK. > > Recently, I need to porting my app from WIN64 to WIN32. As us

Re: [Mingw-w64-public] i686-w64-mingw32-gcc dependency problem (GLIBC_2.14)

2012-09-23 Thread Ruben Van Boxem
2012/9/23 KC > Hi > > I use mingw-w64 WIN64 cross compiler for quite a while under CentOS 6.x > which use glibc-2.12. > (I use this version: mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2) > and everything is OK. > > Recently, I need to porting my app from WIN64 to WIN32. As usual, I want > to

[Mingw-w64-public] i686-w64-mingw32-gcc dependency problem (GLIBC_2.14)

2012-09-23 Thread KC
Hi I use mingw-w64 WIN64 cross compiler for quite a while under CentOS 6.x which use glibc-2.12. (I use this version: mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2) and everything is OK. Recently, I need to porting my app from WIN64 to WIN32. As usual, I want to use WIN32 cross compiler under