From: Pavel K. <pa...@pa...> - 2007-10-16 17:35:25
|
Hi wisers, I am trying to compile a simple windows application but I could not get any result. When the source code contains errors, then the complier detects them and reports properly. However, if there seem to be no errors in the source code, the compiler returns no error message (as expected :-) but no "o" file is produced. Moreover the windres always returns "Error precompiling the source". I have unpacked the bin snapshot archive with directory structure, and added the "bin" folder into global PATH environment variable. I am using Windows XP 64bit. Any idea what I can made wrong? Thanks, Pavel |
From: NightStrike <nig...@gm...> - 2007-10-16 17:48:14
|
On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > Hi wisers, > > I am trying to compile a simple windows application but I could not get > any result. When the source code contains errors, then the complier > detects them and reports properly. However, if there seem to be no > errors in the source code, the compiler returns no error message (as > expected :-) but no "o" file is produced. Moreover the windres always > returns "Error precompiling the source". > > I have unpacked the bin snapshot archive with directory structure, and > added the "bin" folder into global PATH environment variable. I am using > Windows XP 64bit. > > Any idea what I can made wrong? Which archive did you use? There are several. Did you use the native x86_64-pc-mingw32 compiler? |
From: Pavel K. <pa...@pa...> - 2007-10-16 17:57:55
|
NightStrike wrote: > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > >> Hi wisers, >> >> I am trying to compile a simple windows application but I could not get >> any result. When the source code contains errors, then the complier >> detects them and reports properly. However, if there seem to be no >> errors in the source code, the compiler returns no error message (as >> expected :-) but no "o" file is produced. Moreover the windres always >> returns "Error precompiling the source". >> >> I have unpacked the bin snapshot archive with directory structure, and >> added the "bin" folder into global PATH environment variable. I am using >> Windows XP 64bit. >> >> Any idea what I can made wrong? >> > > Which archive did you use? There are several. Did you use the native > x86_64-pc-mingw32 compiler? > > I've used the "Complete Root Environment Snapshot" from http://sourceforge.net/project/showfiles.php?group_id=202880, the file "mingw-w64-bin_x86_64-mingw32_20071013.tar.bz2 <http://downloads.sourceforge.net/mingw-w64/mingw-w64-bin_x86_64-mingw32_20071013.tar.bz2?modtime=1192286501&big_mirror=0>" And one more correction, windres returns "Error preprocessing the source". Thanks, Pavel |
From: NightStrike <nig...@gm...> - 2007-10-16 18:02:59
|
On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > NightStrike wrote: > > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > > > >> Hi wisers, > >> > >> I am trying to compile a simple windows application but I could not get > >> any result. When the source code contains errors, then the complier > >> detects them and reports properly. However, if there seem to be no > >> errors in the source code, the compiler returns no error message (as > >> expected :-) but no "o" file is produced. Moreover the windres always > >> returns "Error precompiling the source". > >> > >> I have unpacked the bin snapshot archive with directory structure, and > >> added the "bin" folder into global PATH environment variable. I am using > >> Windows XP 64bit. > >> > >> Any idea what I can made wrong? > >> > > > > Which archive did you use? There are several. Did you use the native > > x86_64-pc-mingw32 compiler? > > > > > I've used the "Complete Root Environment Snapshot" from > http://sourceforge.net/project/showfiles.php?group_id=202880, the file > "mingw-w64-bin_x86_64-mingw32_20071013.tar.bz2 > <http://downloads.sourceforge.net/mingw-w64/mingw-w64-bin_x86_64-mingw32_20071013.tar.bz2?modtime=1192286501&big_mirror=0>" > > And one more correction, windres returns "Error preprocessing the source". > It's entirely possible that I'm not building that correctly :) Do you have any other platforms you can try? For instance, the cygwin build or the i686-pc-mingw32 build? |
From: NightStrike <nig...@gm...> - 2007-10-16 18:20:53
|
On 10/16/07, NightStrike <nig...@gm...> wrote: > It's entirely possible that I'm not building that correctly :) > > Do you have any other platforms you can try? For instance, the cygwin > build or the i686-pc-mingw32 build? > Also, if you are interested, since you have a native 64-bit windows environment, you may want to build the toolchain yourself. Do the following: mkdir /tmp/rt64 cd /tmp/rt64 svn co https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/experimental/buildsystem scripts Edit the third line in scripts/makebuild.sh: HST=x86_64-pc-linux Set HST to whatever you want, maybe i686-pc-cygwin or whatever your build system happens to be. This variable doesn't really matter anyway, as it's only used in naming the root directory. In fact, you can skip this if you want and just deal with a root called root-x86_64-pc-linux :) (It's experimental, after all) Then just do: scripts/makebuildroot.sh --build Then wait.. ..and wait.. ..and wait some more. When you're done, you should see /tmp/rt64/root-something. That's a root that you can use. It'll be named with whatever you set HST to. You can move that directory structure anywhere, set your paths accordingly, and you should be good to go. |
From: Pavel K. <pa...@pa...> - 2007-10-16 19:08:11
|
NightStrike wrote: > On 10/16/07, NightStrike <nig...@gm...> wrote: > >> It's entirely possible that I'm not building that correctly :) >> >> Do you have any other platforms you can try? For instance, the cygwin >> build or the i686-pc-mingw32 build? >> >> > > Also, if you are interested, since you have a native 64-bit windows > environment, you may want to build the toolchain yourself. Do the > following: > > mkdir /tmp/rt64 > cd /tmp/rt64 > svn co https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/experimental/buildsystem > scripts > > Edit the third line in scripts/makebuild.sh: > HST=x86_64-pc-linux > Set HST to whatever you want, maybe i686-pc-cygwin or whatever your > build system happens to be. This variable doesn't really matter > anyway, as it's only used in naming the root directory. In fact, you > can skip this if you want and just deal with a root called > root-x86_64-pc-linux :) (It's experimental, after all) > > Then just do: > scripts/makebuildroot.sh --build > > Then wait.. > ..and wait.. > ..and wait some more. > > When you're done, you should see /tmp/rt64/root-something. That's a > root that you can use. It'll be named with whatever you set HST to. > You can move that directory structure anywhere, set your paths > accordingly, and you should be good to go. > > Thank you for the hint. I am trying to make a test build on linux at the moment. I don't think I would manage this on Windows. I have no sh, csv, svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows (besides Delphi, MSVC++, and others which are either useless or I don't want to use). An optimal solution would be to compile 32 bit mingw with 64 bit cross-compiler (there perhaps exists one already, I am not using the latest build) and then use this to compile mingw-w64. |
From: NightStrike <nig...@gm...> - 2007-10-16 19:19:19
|
On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > Thank you for the hint. I am trying to make a test build on linux at the > moment. I don't think I would manage this on Windows. I have no sh, csv, > svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows > (besides Delphi, MSVC++, and others which are either useless or I don't > want to use). An optimal solution would be to compile 32 bit mingw with > 64 bit cross-compiler (there perhaps exists one already, I am not using > the latest build) and then use this to compile mingw-w64. That is what we currently do. I use an x86_64-pc-linux system to do most of my work, as it's blazing fast. The environment you downloaded was a canadian cross from that system to x86_64-pc-mingw32 native. It apparently doesn't work well :) |
From: Pavel K. <pa...@pa...> - 2007-10-16 19:54:46
|
NightStrike wrote: > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > >> Thank you for the hint. I am trying to make a test build on linux at the >> moment. I don't think I would manage this on Windows. I have no sh, csv, >> svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows >> (besides Delphi, MSVC++, and others which are either useless or I don't >> want to use). An optimal solution would be to compile 32 bit mingw with >> 64 bit cross-compiler (there perhaps exists one already, I am not using >> the latest build) and then use this to compile mingw-w64. >> > > That is what we currently do. I use an x86_64-pc-linux system to do > most of my work, as it's blazing fast. The environment you downloaded > was a canadian cross from that system to x86_64-pc-mingw32 native. It > apparently doesn't work well :) > > The first build has failed because I missed the texinfo package. I'll download it and give a second try, but not until tomorrow. Thanks, Pavel |
From: NightStrike <nig...@gm...> - 2008-01-13 09:14:41
|
On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > NightStrike wrote: > > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > > > >> Thank you for the hint. I am trying to make a test build on linux at the > >> moment. I don't think I would manage this on Windows. I have no sh, csv, > >> svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows > >> (besides Delphi, MSVC++, and others which are either useless or I don't > >> want to use). An optimal solution would be to compile 32 bit mingw with > >> 64 bit cross-compiler (there perhaps exists one already, I am not using > >> the latest build) and then use this to compile mingw-w64. > >> > > > > That is what we currently do. I use an x86_64-pc-linux system to do > > most of my work, as it's blazing fast. The environment you downloaded > > was a canadian cross from that system to x86_64-pc-mingw32 native. It > > apparently doesn't work well :) > > > > > The first build has failed because I missed the texinfo package. I'll > download it and give a second try, but not until tomorrow. Thanks, Pavel > Pavel, Have you had success in your endeavor? |
From: Pavel K. <pa...@pa...> - 2008-02-03 20:25:36
|
NightStrike wrote: > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > >> NightStrike wrote: >> >>> On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: >>> >>> >>>> Thank you for the hint. I am trying to make a test build on linux at the >>>> moment. I don't think I would manage this on Windows. I have no sh, csv, >>>> svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows >>>> (besides Delphi, MSVC++, and others which are either useless or I don't >>>> want to use). An optimal solution would be to compile 32 bit mingw with >>>> 64 bit cross-compiler (there perhaps exists one already, I am not using >>>> the latest build) and then use this to compile mingw-w64. >>>> >>>> >>> That is what we currently do. I use an x86_64-pc-linux system to do >>> most of my work, as it's blazing fast. The environment you downloaded >>> was a canadian cross from that system to x86_64-pc-mingw32 native. It >>> apparently doesn't work well :) >>> >>> >>> >> The first build has failed because I missed the texinfo package. I'll >> download it and give a second try, but not until tomorrow. Thanks, Pavel >> >> > > Pavel, > > Have you had success in your endeavor? > > NightStrike, sorry for a late reply. I didn't make a big progress since my last post to the forum. Being engaged by other stuff I decided to postpone my 64bit activities, until I really need it. Recently I tried to download the newest build, but got similar results on Windows XP 64bit. I could not get windres running at all, and gcc seems to be unable to bite the WinMain function. I can send you my very simple windows application, which I am experimenting with, along with the error messages I am getting. If somebody is interested in. Thanks, Pavel |
From: NightStrike <nig...@gm...> - 2008-02-03 20:26:34
|
On 2/3/08, Pavel Krejcir <pa...@pa...> wrote: > NightStrike wrote: > > On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > > > >> NightStrike wrote: > >> > >>> On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: > >>> > >>> > >>>> Thank you for the hint. I am trying to make a test build on linux at the > >>>> moment. I don't think I would manage this on Windows. I have no sh, csv, > >>>> svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows > >>>> (besides Delphi, MSVC++, and others which are either useless or I don't > >>>> want to use). An optimal solution would be to compile 32 bit mingw with > >>>> 64 bit cross-compiler (there perhaps exists one already, I am not using > >>>> the latest build) and then use this to compile mingw-w64. > >>>> > >>>> > >>> That is what we currently do. I use an x86_64-pc-linux system to do > >>> most of my work, as it's blazing fast. The environment you downloaded > >>> was a canadian cross from that system to x86_64-pc-mingw32 native. It > >>> apparently doesn't work well :) > >>> > >>> > >>> > >> The first build has failed because I missed the texinfo package. I'll > >> download it and give a second try, but not until tomorrow. Thanks, Pavel > >> > >> > > > > Pavel, > > > > Have you had success in your endeavor? > > > > > NightStrike, > > sorry for a late reply. I didn't make a big progress since my last post > to the forum. Being engaged by other stuff I decided to postpone my > 64bit activities, until I really need it. Recently I tried to download > the newest build, but got similar results on Windows XP 64bit. I could > not get windres running at all, and gcc seems to be unable to bite the > WinMain function. I can send you my very simple windows application, > which I am experimenting with, along with the error messages I am > getting. If somebody is interested in. > > Thanks, Pavel > Thank you, that would be very helpful if you could provide any examples of code that won't compile. |
From: Pavel K. <pa...@pa...> - 2008-02-08 08:19:57
Attachments:
MenuTestMinGW64.tar.gz
|
NightStrike wrote: > On 2/3/08, Pavel Krejcir <pa...@pa...> wrote: > >> NightStrike wrote: >> >>> On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: >>> >>> >>>> NightStrike wrote: >>>> >>>> >>>>> On 10/16/07, Pavel Krejcir <pa...@pa...> wrote: >>>>> >>>>> >>>>> >>>>>> Thank you for the hint. I am trying to make a test build on linux at the >>>>>> moment. I don't think I would manage this on Windows. I have no sh, csv, >>>>>> svn, cygwin etc. MinGW 32 is the only compiler I can use on Windows >>>>>> (besides Delphi, MSVC++, and others which are either useless or I don't >>>>>> want to use). An optimal solution would be to compile 32 bit mingw with >>>>>> 64 bit cross-compiler (there perhaps exists one already, I am not using >>>>>> the latest build) and then use this to compile mingw-w64. >>>>>> >>>>>> >>>>>> >>>>> That is what we currently do. I use an x86_64-pc-linux system to do >>>>> most of my work, as it's blazing fast. The environment you downloaded >>>>> was a canadian cross from that system to x86_64-pc-mingw32 native. It >>>>> apparently doesn't work well :) >>>>> >>>>> >>>>> >>>>> >>>> The first build has failed because I missed the texinfo package. I'll >>>> download it and give a second try, but not until tomorrow. Thanks, Pavel >>>> >>>> >>>> >>> Pavel, >>> >>> Have you had success in your endeavor? >>> >>> >>> >> NightStrike, >> >> sorry for a late reply. I didn't make a big progress since my last post >> to the forum. Being engaged by other stuff I decided to postpone my >> 64bit activities, until I really need it. Recently I tried to download >> the newest build, but got similar results on Windows XP 64bit. I could >> not get windres running at all, and gcc seems to be unable to bite the >> WinMain function. I can send you my very simple windows application, >> which I am experimenting with, along with the error messages I am >> getting. If somebody is interested in. >> >> Thanks, Pavel >> >> > > Thank you, that would be very helpful if you could provide any > examples of code that won't compile. > > Attached you will find my example. I don't use makefile (there seems to be no make available for 64bit yet), the compilation is invoked from the bat file, at command prompt as: compile 2> compres.log The compres.log file is attached. The line "x86_64-pc-mingw32-gcc-4.3.0.exe: : No such file or directory" comes from windres, so it apparently expects some specific version of gcc. The build used is "mingw-w64-bin_x86_64-mingw_20080116.tar.bz2". The project can be easily compiled with mingw32, if the windows callback function headers are changed to the commented versions. I hope this will either help you, or somebody will be able to explain me what I am doing wrong :-) Thanks, Pavel |
From: Kai T. <Kai...@on...> - 2008-02-08 13:59:50
|
Thank you all for your help. I isolated the problem and found that there were two different problems by the native build: 1) While compiling the native compiler the symbolic link mingw have to be set on the x86_64-pc-mingw32 directory. After the compile this link can be removed. This is reasoned by a broken gcc configure for this target. 2) The mpfr and the gmp libraries need to be compiled out-side of the bootstrap. See on the Wiki Page the link to the patch necessary. Otherwise it falls back to a 'none-pc-mingw32' ??? configuration, which is at the very end something compilable and linkable, but not working :( I will add soon the precompiled gmp and mpfr plus headers to our bin release. So we can spare to do this again and again. Also there will be today an update version of the mingw-w64-bin-x86_64-mingw... toolchain. I tested it and for me it worked ;) Cheers, i.A. Kai Tietz | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | (")_(") world domination. |
From: NightStrike <nig...@gm...> - 2008-02-08 14:56:32
|
On 2/8/08, Kai Tietz <Kai...@on...> wrote: > Thank you all for your help. I isolated the problem and found that there > were two different problems by the native build: > 1) While compiling the native compiler the symbolic link mingw have to be > set on the x86_64-pc-mingw32 directory. > After the compile this link can be removed. This is reasoned by a broken > gcc configure for this target. > 2) The mpfr and the gmp libraries need to be compiled out-side of the > bootstrap. See on the Wiki Page the link to the patch necessary. > Otherwise it falls back to a 'none-pc-mingw32' ??? configuration, which > is at the very end something compilable and linkable, but not working :( > > I will add soon the precompiled gmp and mpfr plus headers to our bin > release. So we can spare to do this again and again. > Also there will be today an update version of the > mingw-w64-bin-x86_64-mingw... toolchain. I tested it and for me it worked > ;) This should be something that we fix in gcc in terms of how it compiles gmp and mpfr. There's no reason why it can't pass the entire host string to gmp instead of just the last part of the triplet. Of course, this also requires patching gmp, and that doesn't seem very likely. I still haven't received a response on their mailing list. |
From: Kai T. <Kai...@on...> - 2008-02-08 15:05:13
|
NightStrike, > On 2/8/08, Kai Tietz <Kai...@on...> wrote: > > Thank you all for your help. I isolated the problem and found that there > > were two different problems by the native build: > > 1) While compiling the native compiler the symbolic link mingw have to be > > set on the x86_64-pc-mingw32 directory. > > After the compile this link can be removed. This is reasoned by a broken > > gcc configure for this target. > > 2) The mpfr and the gmp libraries need to be compiled out-side of the > > bootstrap. See on the Wiki Page the link to the patch necessary. > > Otherwise it falls back to a 'none-pc-mingw32' ??? configuration, which > > is at the very end something compilable and linkable, but not working :( > > > > I will add soon the precompiled gmp and mpfr plus headers to our bin > > release. So we can spare to do this again and again. > > Also there will be today an update version of the > > mingw-w64-bin-x86_64-mingw... toolchain. I tested it and for me it worked > > ;) > > This should be something that we fix in gcc in terms of how it > compiles gmp and mpfr. There's no reason why it can't pass the entire > host string to gmp instead of just the last part of the triplet. Of > course, this also requires patching gmp, and that doesn't seem very > likely. I still haven't received a response on their mailing list. Yes, this is a task for gcc 4.4. I think for the time being, we should use the precompiled gmp and mpfr libraries. Yes, it seems that they didn't check their bug mailing list very often, or they are slow in anwsering. ;) BTW: I uploaded the new bin package. I missed for the first release to build binutils with --with-sysroot, therefore I had to update it a second time. Cheers, i.A. Kai Tietz | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | (")_(") world domination. ------------------------------------------------------------------------------------------ OneVision Software Entwicklungs GmbH & Co. KG Dr.-Leo-Ritter-Straße 9 - 93049 Regensburg Tel: +49.(0)941.78004.0 - Fax: +49.(0)941.78004.489 - www.OneVision.com Commerzbank Regensburg - BLZ 750 400 62 - Konto 6011050 Handelsregister: HRA 6744, Amtsgericht Regensburg Komplementärin: OneVision Software Entwicklungs Verwaltungs GmbH Dr.-Leo-Ritter-Straße 9 – 93049 Regensburg Handelsregister: HRB 8932, Amtsgericht Regensburg - Geschäftsführer: Ulrike Döhler, Manuela Kluger |