From: whatis n. <wha...@go...> - 2008-03-20 11:56:21
|
Hi, gcc isn't working on this install of mingw-w64-bin-x86_64-mingw_20080213 on my OS. The OS is Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2 The install is on C:\MinGW in MSYS: $ gcc --version gcc.exe (GCC) 4.3.0 20080131 (experimental) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Now when I compile: //#include <iostream> #include <stdio.h> int main(int argc, char* argv[]) { printf("%i bit build\n", sizeof(void*)*8); return 0; } with gcc, (gcc test.c) nothing happens... nore does it work with g++ However if I include <iostream> it works with g++ $ g++ test.cpp $ a.exe 64 bit build The same problem occurs when I run those commands in windows command prompt... I ran the exact same test on a win32 machine, and it all worked as expected. What is the problem? Sorry I realise this email doesn't contain a very detailed description of my setup, but if there is any more information I can send you please let me know. My aim is to build a bunch of libraries in 64 bit, such as libsndfile, libjpeg, libtiff etc. Thanks in advance. Regards. |
From: NightStrike <nig...@gm...> - 2008-03-20 12:45:59
|
On 3/20/08, whatis neveritis <wha...@go...> wrote: > $ gcc --version > gcc.exe (GCC) 4.3.0 20080131 (experimental) > What is the problem? This is an old version. I'll build a new version and upload it to the site, hopefully in the next few hours. Try that, and then we'll go from there. I have to admit, it was a little surprising that g++ worked and gcc didn't. Usually, it's the other way around. On that note, btw, g++ and gfortran don't work too well, and don't give a lot of feedback that they don't work. |
From: NightStrike <nig...@gm...> - 2008-03-20 14:09:01
|
On 3/20/08, NightStrike <nig...@gm...> wrote: > On 3/20/08, whatis neveritis <wha...@go...> wrote: > > $ gcc --version > > gcc.exe (GCC) 4.3.0 20080131 (experimental) > > > What is the problem? > > This is an old version. I'll build a new version and upload it to the > site, hopefully in the next few hours. Try that, and then we'll go > from there. > > I have to admit, it was a little surprising that g++ worked and gcc > didn't. Usually, it's the other way around. On that note, btw, g++ > and gfortran don't work too well, and don't give a lot of feedback > that they don't work. Ok, go get 'em, tiger. Find them at your friendly download section now. (Ok, well, I'm posting this as it's uploading, so it'll be in a few minutes..) |
From: Aaron G. <aa...@aa...> - 2008-03-20 14:28:54
|
Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? Aaron -- > -----Original Message----- > From: min...@li... [mailto:mingw-w64- > pub...@li...] On Behalf Of NightStrike > Sent: Thursday, March 20, 2008 7:15 AM > To: whatis neveritis; Kai Tietz > Cc: min...@li... > Subject: Re: [Mingw-w64-public] gcc and g++ (c compilation only) not > workingon MinGW-64 in Microsoft Windows XP Professional x64 > Edition(Version 2003) Service Pack 2 > > On 3/20/08, NightStrike <nig...@gm...> wrote: > > On 3/20/08, whatis neveritis <wha...@go...> wrote: > > > $ gcc --version > > > gcc.exe (GCC) 4.3.0 20080131 (experimental) > > > > > What is the problem? > > > > This is an old version. I'll build a new version and upload it to > the > > site, hopefully in the next few hours. Try that, and then we'll go > > from there. > > > > I have to admit, it was a little surprising that g++ worked and gcc > > didn't. Usually, it's the other way around. On that note, btw, g++ > > and gfortran don't work too well, and don't give a lot of feedback > > that they don't work. > > Ok, go get 'em, tiger. Find them at your friendly download section > now. > > (Ok, well, I'm posting this as it's uploading, so it'll be in a few > minutes..) > > ----------------------------------------------------------------------- > -- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |
From: NightStrike <nig...@gm...> - 2008-03-20 14:30:46
|
On 3/20/08, Aaron Giles <aa...@aa...> wrote: > Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? > > Aaron Yeah, I'm gonna go with a 'No' on that one.... But feel free to try it :) :) I suppose I should add Vista to the list of hosts I build toolchains for........ Does anyone know (Kai?) if I can do the -D thing for *ANY* target? ie, is there ever a case where we would require that it *NOT* be defined? There was discussion about that somewhere on the mingw list. If we can make it so that it builds the same everywhere, then we'll never need to define that again. |
From: FX C. <fxc...@gm...> - 2008-03-20 14:38:20
|
>> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? That fix has been included in the build system of GCC itself for quite a few months now. You don't need to do anything special to benefit from it (apart from using recent mingw headers along). FX -- François-Xavier Coudert http://www.homepages.ucl.ac.uk/~uccafco/ |
From: NightStrike <nig...@gm...> - 2008-03-20 14:39:33
|
On 3/20/08, FX Coudert <fxc...@gm...> wrote: > >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? > > That fix has been included in the build system of GCC itself for > quite a few months now. You don't need to do anything special to > benefit from it (apart from using recent mingw headers along). Can you elaborate on that? How does gcc for instance know if you're targetting a Vista platform? |
From: FX C. <fxc...@gm...> - 2008-03-20 14:50:26
|
> Can you elaborate on that? How does gcc for instance know if you're > targetting a Vista platform? See http://gcc.gnu.org/ml/fortran/2008-03/msg00119.html and http:// gcc.gnu.org/ml/fortran/2008-03/msg00120.html The fix is applied to all mingw hosts. FX -- François-Xavier Coudert http://www.homepages.ucl.ac.uk/~uccafco/ |
From: Aaron G. <aa...@aa...> - 2008-03-20 14:53:24
|
> On 3/20/08, Aaron Giles <aa...@aa...> wrote: > > Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? > > Yeah, I'm gonna go with a 'No' on that one.... But feel free to try > it :) :) > > I suppose I should add Vista to the list of hosts I build toolchains > for........ No, all you need to do is make sure that define is set for any Windows-based toolchains. I don't know if having it set will foul up any of the Linux builds or not. Aaron |
From: whatis n. <wha...@go...> - 2008-03-20 15:12:38
|
> > Ok, go get 'em, tiger. Find them at your friendly download section now. > > (Ok, well, I'm posting this as it's uploading, so it'll be in a few > minutes..) > OK thanks NightStrike. I've downloaded mingw-w64-bin-x86_64-mingw_20080320, and installed it into an empty c:\mingw directory $ g++ --version g++.exe (GCC) 4.4.0 20080320 (experimental) Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ g++ test.cpp this command doesn't produce an a.exe, with or without including <iostream> $ gcc testc.cpp however this one does when the code is c.. (although it doesn't give an error message when I include <iostream> it just silently fails). So I guess this is a progression on the gcc front, but a regression on the g++ front.. What do you recommend I do? copy g++ from the old build into this one? my libraries need both compiles to work before they'll compile. :( Thanks for your time. |
From: NightStrike <nig...@gm...> - 2008-03-20 15:17:06
|
On 3/20/08, whatis neveritis <wha...@go...> wrote: > > > Ok, go get 'em, tiger. Find them at your friendly download section now. > > > > (Ok, well, I'm posting this as it's uploading, so it'll be in a few > minutes..) > > > > OK thanks NightStrike. I've downloaded > mingw-w64-bin-x86_64-mingw_20080320, and installed it into > an empty c:\mingw directory > > $ g++ --version > g++.exe (GCC) 4.4.0 20080320 (experimental) > Copyright (C) 2008 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > $ g++ test.cpp > > this command doesn't produce an a.exe, with or without including <iostream> I thought we fixed iostream...... Let me think.... Kai, did you ever get all those patches into the trunk for this? If not, that would explain it. It's not really a regression for g++; more like a patch I forgot to apply. > $ gcc testc.cpp > > however this one does when the code is c.. (although it doesn't give an > error message when I include <iostream> it just silently fails). > > So I guess this is a progression on the gcc front, but a regression on the > g++ front.. > > What do you recommend I do? copy g++ from the old build into this one? my > libraries need both compiles to work before they'll compile. :( Hold out a little longer :) We did something to fix iostream (although I'll remind you that most of g++ and all of gfortran is broken), and I don't remember what. I need a patch from Kai, and I forget which one. Honestly, can you just use the cross compilers? They work great. |
From: Kai T. <Kai...@on...> - 2008-03-20 15:22:49
|
min...@li... wrote on 20.03.2008 16:17:04: > On 3/20/08, whatis neveritis <wha...@go...> wrote: > > > > > Ok, go get 'em, tiger. Find them at your friendly download section now. > > > > > > (Ok, well, I'm posting this as it's uploading, so it'll be in a few > > minutes..) > > > > > > > OK thanks NightStrike. I've downloaded > > mingw-w64-bin-x86_64-mingw_20080320, and installed it into > > an empty c:\mingw directory > > > > $ g++ --version > > g++.exe (GCC) 4.4.0 20080320 (experimental) > > Copyright (C) 2008 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > > $ g++ test.cpp > > > > this command doesn't produce an a.exe, with or without including <iostream> > > I thought we fixed iostream...... > > Let me think.... > > > Kai, did you ever get all those patches into the trunk for this? If > not, that would explain it. It's not really a regression for g++; > more like a patch I forgot to apply. > > > $ gcc testc.cpp > > > > however this one does when the code is c.. (although it doesn't give an > > error message when I include <iostream> it just silently fails). > > > > So I guess this is a progression on the gcc front, but a regression on the > > g++ front.. > > > > What do you recommend I do? copy g++ from the old build into this one? my > > libraries need both compiles to work before they'll compile. :( > > Hold out a little longer :) > > We did something to fix iostream (although I'll remind you that most > of g++ and all of gfortran is broken), and I don't remember what. I > need a patch from Kai, and I forget which one. It was the disabling of stack probing AFAI remember. Cheers Kai | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | (")_(") world domination. |
From: NightStrike <nig...@gm...> - 2008-03-20 15:23:21
|
On 3/20/08, Kai Tietz <Kai...@on...> wrote: > > We did something to fix iostream (although I'll remind you that most > > of g++ and all of gfortran is broken), and I don't remember what. I > > need a patch from Kai, and I forget which one. > > It was the disabling of stack probing AFAI remember. Yeah, that was it... do you have a patch for that? Did you ever submit it to gcc? |
From: Kai T. <Kai...@on...> - 2008-03-20 15:26:44
|
NightStrike <nig...@gm...> wrote on 20.03.2008 16:23:17: > On 3/20/08, Kai Tietz <Kai...@on...> wrote: > > > We did something to fix iostream (although I'll remind you that most > > > of g++ and all of gfortran is broken), and I don't remember what. I > > > need a patch from Kai, and I forget which one. > > > > It was the disabling of stack probing AFAI remember. > > Yeah, that was it... do you have a patch for that? Did you ever > submit it to gcc? No, this patch is more a hack. The __chkstk has to be fixed not simply turned off :) Cheers, Kai | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | (")_(") world domination. |
From: NightStrike <nig...@gm...> - 2008-03-20 15:27:21
|
On 3/20/08, Kai Tietz <Kai...@on...> wrote: > NightStrike <nig...@gm...> wrote on 20.03.2008 16:23:17: > > > On 3/20/08, Kai Tietz <Kai...@on...> wrote: > > > > We did something to fix iostream (although I'll remind you that most > > > > of g++ and all of gfortran is broken), and I don't remember what. I > > > > need a patch from Kai, and I forget which one. > > > > > > It was the disabling of stack probing AFAI remember. > > > > Yeah, that was it... do you have a patch for that? Did you ever > > submit it to gcc? > No, this patch is more a hack. The __chkstk has to be fixed not simply > turned off :) Is there a gcc bug report opened? |
From: Kai T. <Kai...@on...> - 2008-03-20 15:33:16
|
NightStrike <nig...@gm...> wrote on 20.03.2008 16:27:17: > On 3/20/08, Kai Tietz <Kai...@on...> wrote: > > NightStrike <nig...@gm...> wrote on 20.03.2008 16:23:17: > > > > > On 3/20/08, Kai Tietz <Kai...@on...> wrote: > > > > > We did something to fix iostream (although I'll remind you that most > > > > > of g++ and all of gfortran is broken), and I don't remember what. I > > > > > need a patch from Kai, and I forget which one. > > > > > > > > It was the disabling of stack probing AFAI remember. > > > > > > Yeah, that was it... do you have a patch for that? Did you ever > > > submit it to gcc? > > No, this patch is more a hack. The __chkstk has to be fixed not simply > > turned off :) > > Is there a gcc bug report opened? AFAIK yes. It was about the patch for __alloca. I am still on to find the point, which is responsible for the stack clobbering. Joseph's patch has solved some problems, as the guys with the fortran compiler told. I assume the major point for our native build are gmp/mpfr compilation failures. Btw, the patches I sent you today requires an rebuild of those libraries for native. Cheers, Kai |
From: FX C. <fxc...@gm...> - 2008-03-20 15:36:11
|
> I assume the major point for our native build are gmp/mpfr compilation > failures. I'm sorry if I say something stupid, but: have you tried building gmp and mpfr with --host=none-none-none? PS: I have another question: what is the roadmap for merging the headers and crt with 32-bit mingw? FX -- François-Xavier Coudert http://www.homepages.ucl.ac.uk/~uccafco/ |
From: Kai T. <Kai...@on...> - 2008-03-20 15:43:43
|
FX Coudert <fxc...@gm...> wrote on 20.03.2008 16:36:00: > > I assume the major point for our native build are gmp/mpfr compilation > > failures. > > I'm sorry if I say something stupid, but: have you tried building gmp > and mpfr with --host=none-none-none? May, we should give it a try. But the major problem is, that gmp and mpfr assumes on some places, that long has 64-bit width, which is for this target certainly wrong :( > PS: I have another question: what is the roadmap for merging the > headers and crt with 32-bit mingw? IMHO first the stack clobbering problem has to be solved. But if we reach this state, we will continue merging. I think you point specially on the mingw_snprintf feature for libgfortran. This will be next. Cheers, Kai |
From: NightStrike <nig...@gm...> - 2008-03-20 15:38:04
|
On 3/20/08, FX Coudert <fxc...@gm...> wrote: > PS: I have another question: what is the roadmap for merging the > headers and crt with 32-bit mingw? You're a funny guy :) :) :) |
From: FX C. <fxc...@gm...> - 2008-03-20 15:42:18
|
>> PS: I have another question: what is the roadmap for merging the >> headers and crt with 32-bit mingw? > > You're a funny guy :) :) :) Shall I understand that as a "not planned yet"? FX -- François-Xavier Coudert http://www.homepages.ucl.ac.uk/~uccafco/ |
From: Aaron G. <aa...@aa...> - 2008-03-20 15:17:28
|
> >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? > > That fix has been included in the build system of GCC itself for > quite a few months now. You don't need to do anything special to > benefit from it (apart from using recent mingw headers along). Apparently so, as I was able to compile a hello world app for the first time. :) Now for some more serious testing.... Aaron |
From: NightStrike <nig...@gm...> - 2008-03-20 15:19:25
|
On 3/20/08, Aaron Giles <aa...@aa...> wrote: > > >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)? > > > > That fix has been included in the build system of GCC itself for > > quite a few months now. You don't need to do anything special to > > benefit from it (apart from using recent mingw headers along). > > Apparently so, as I was able to compile a hello world app for the first > time. :) > > Now for some more serious testing.... Tread carefully :) Keep in mind that gcc works much better than g++/gfortran. |
From: whatis n. <wha...@go...> - 2008-03-20 15:21:59
|
> > Honestly, can you just use the cross compilers? They work great. > Hi, yes that is absolutely an option, however I'm not too sure how to get that up and running. I've got more than enough win32 machines around me, although not too sure how to get gcc to compile in 64 bit on it.. so far when I tried it said: test.c:1: sorry, unimplemented: 64-bit mode not compiled in I'm guessing I need to download it from somewhere. |
From: NightStrike <nig...@gm...> - 2008-03-20 15:25:11
|
On 3/20/08, whatis neveritis <wha...@go...> wrote: > > > Honestly, can you just use the cross compilers? They work great. > > > > > Hi, yes that is absolutely an option, however I'm not too sure how to get > that up and running. I've got more than enough win32 machines around me, > although not too sure how to get gcc to compile in 64 bit on it.. so far > when I tried it said: > > test.c:1: sorry, unimplemented: 64-bit mode not compiled in > > I'm guessing I need to download it from somewhere. Yup. In the download area, I build 5 toolchains, hosted on these systems: Linux32 Linux64 Win32 Win64 Cygwin32 Pick your poison. You should be able to run the Win32 one (look for i686-mingw) on a Win64 host. It'll run it in the WoW simulator. I personally use the Linux64 cross compiler for all of my work, so its kept most up to date. |
From: whatis n. <wha...@go...> - 2008-03-20 16:00:19
|
On Thu, Mar 20, 2008 at 3:25 PM, NightStrike <nig...@gm...> wrote: > On 3/20/08, whatis neveritis <wha...@go...> wrote: > > > > > Honestly, can you just use the cross compilers? They work great. > [...] > > I'm guessing I need to download it from somewhere. > > Yup. In the download area, I build 5 toolchains, hosted on these systems: > > Linux32 > Linux64 > Win32 > Win64 > Cygwin32 > > Pick your poison. You should be able to run the Win32 one (look for > i686-mingw) on a Win64 host. It'll run it in the WoW simulator. I > personally use the Linux64 cross compiler for all of my work, so its > kept most up to date. > Just to be sure, are we talking about the download section for MinGW-w64 "Complete toolchain snapshot"? It seems you're referring to "mingw-w64-bin_i686-mingw_20080116", which I've downloaded and tested right away. First off I get a message from winrar telling me the symbolic links are broken. Secondly I notice the files have long prefixes in the c:\mingw\bin directory, for example "x86_64-pc-mingw32-c++filt.exe", I also notice there are more bins in C:\mingw\x86_64-pc-mingw32\bin, such as g++ I tried out that g++ but I got: "g++.exe: CreateProcess: No such file or directory" I don't think mingw and msys work well on WoW all together, at least in my experience, the 32 stuff has to be run on a 32 but OS, and vice versa for 64 bit. |