Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 2010-06-15 6:49 AM, Ruben Van Boxem wrote: snippity-snip That's exactly why I said MSYS is special... and I don't know what will break if I try to fix it. I still find it very odd that GMP configure even knows about the name link, because no mingw toolchain even has such a thing. Shouldn't the script use ld or something else for its tests? link.exe is the MSVC toolchain's equivalent of ld. Oddly, it looks like -dump -symbols makes it act like nm - even though the binary you're supposed to be using is called dumpbin.exe. Perhaps it's some funny backwards-compatibility thing? Either way, without more of the config log it's difficult to tell why it's trying to use a half-msvc toolchain. -- Mook -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 6/16/2010 18:51, Ruben Van Boxem wrote: Either way, without more of the config log it's difficult to tell why it's trying to use a half-msvc toolchain. I have attached stderr and stdout logs for configure --host=x86_64-w64-mingw32 --disable-shared --enable-alloca=no the config.log file would give more info. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
2010/6/14 Andreas Fabri andreas.fa...@geometryfactory.com Hello, I try to install mingw-64, msys, and gmp 5.0.1 I follow the explanation gven by Ruben Van Boxem vanboxem.ru...@gm.. in the mailing list (I removed the prefix of the .exe files though) https://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTilI0Pv5dbWeckloeDyjbOwSUJBEGYwpCwQbpIRq%40mail.gmail.comforum_name=mingw-w64-public and I get stuck with an error message. Any help is welcome. Best regards, Andreas Fabri $ ./configure --enable-shared --disable-static --enable-alloca=no --host=x86_64 -w64-mingw32 configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking build system type... core2-pc-mingw32 First, to get people reading this list to use our wiki page: http://sourceforge.net/apps/trac/mingw-w64/wiki/MSYS It mentions the solution I describe below for your problem. Some oddities: -- - build system type should always be reported as i686-pc-mingw32, but I'm assuming this is a typo. - It might be necessary to keep a copy of the prefixed toolchain (the x86_64-w64-mingw32-gcc.exe and so forth), especially when using MSYS because you are *essentially* crosscompiling. If you hate renaming everything and don't *need* GCC 4.5, use sezero's toolchains, they are MSYS-ready so to speak (contain both prefixed and unprefixed copies). - I tried configuring GMP and am also having trouble. It seems configure is not pleased with ld or gcc/g++ as a linker (should be reported imho, link.exe is a coreutils app, not part of any toolchain). A solution: I just built GMP successfully: configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --enable-shared --disable-static --enable-alloca=no make make check make install The target is not necessary for most other builds, but apparantly GMP requires it. FYI: I have uploaded my compile of GMP 5.0.1 for x64 Windows. Just unzip the x86_64-w64-mingw32 folder to your mingw64 folder (so that the lib, bin and include folders match up of course). This failed the one test that has been patched upstream, but the bug was in the test itself, the build and library itself is fine (see this threadhttps://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTilYfIjBVRPLt645F14gLERcp9-2hVCMF-azj0Qr%40mail.gmail.comforum_name=mingw-w64-publicfor an explanation). -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
2010/6/15 Ruben Van Boxem vanboxem.ru...@gmail.com 2010/6/14 Andreas Fabri andreas.fa...@geometryfactory.com Hello, I try to install mingw-64, msys, and gmp 5.0.1 I follow the explanation gven by Ruben Van Boxem vanboxem.ru...@gm.. in the mailing list (I removed the prefix of the .exe files though) https://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTilI0Pv5dbWeckloeDyjbOwSUJBEGYwpCwQbpIRq%40mail.gmail.comforum_name=mingw-w64-public and I get stuck with an error message. Any help is welcome. Best regards, Andreas Fabri $ ./configure --enable-shared --disable-static --enable-alloca=no --host=x86_64 -w64-mingw32 configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking build system type... core2-pc-mingw32 First, to get people reading this list to use our wiki page: http://sourceforge.net/apps/trac/mingw-w64/wiki/MSYS It mentions the solution I describe below for your problem. Some oddities: -- - build system type should always be reported as i686-pc-mingw32, but I'm assuming this is a typo. - It might be necessary to keep a copy of the prefixed toolchain (the x86_64-w64-mingw32-gcc.exe and so forth), especially when using MSYS because you are *essentially* crosscompiling. If you hate renaming everything and don't *need* GCC 4.5, use sezero's toolchains, they are MSYS-ready so to speak (contain both prefixed and unprefixed copies). - I tried configuring GMP and am also having trouble. It seems configure is not pleased with ld or gcc/g++ as a linker (should be reported imho, link.exe is a coreutils app, not part of any toolchain). A solution: I just built GMP successfully: configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --enable-shared --disable-static --enable-alloca=no make make check make install The target is not necessary for most other builds, but apparantly GMP requires it. FYI: I have uploaded my compile of GMP 5.0.1 for x64 Windows. Just unzip the x86_64-w64-mingw32 folder to your mingw64 folder (so that the lib, bin and include folders match up of course). This failed the one test that has been patched upstream, but the bug was in the test itself, the build and library itself is fine (see this threadhttps://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTilYfIjBVRPLt645F14gLERcp9-2hVCMF-azj0Qr%40mail.gmail.comforum_name=mingw-w64-publicfor an explanation). (slaps himself on forehead) You'll need to delete link.exe from msys/bin for this to work. I'll try to find out if there is a better solution. You can always use the fresh binaries now :) -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
2010/6/15 JonY jo...@users.sourceforge.net No, not a typo, its GMP configure trying to be smart. :D I didn't have such issues cross compiling GMP in Cygwin or Linux. Well, MSYS is special :s (see other thread on my link.exe removal). Don't you mean --build? Yeah, pretty sure I mean --target (although --host should be equal to target if the latter is unspecified). http://www.linuxquestions.org/questions/slackware-14/explaining-build-host-target-509739/ This tells me --target is useless for anything but gcc itself, and build should always be i686-pc-mingw32, which it is: $ configure --host=x86_64-w64-mingw32 configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking build system type... i686-pc-mingw32 checking host system type... x86_64-w64-mingw32 -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 6/15/2010 20:30, Ruben Van Boxem wrote: 2010/6/15 JonYjo...@users.sourceforge.net On 6/15/2010 19:31, Ruben Van Boxem wrote: I didn't have such issues cross compiling GMP in Cygwin or Linux. Well, MSYS is special :s (see other thread on my link.exe removal). MSYS is not special at all to configure scripts. How does your PATH look? I am very puzzled how this can happen. I know this, I meant the precautions and gotcha's MSYS sometimes has, like the link.exe issue we are having here. My PATH from within MSYS is this: .:/usr/local/bin:/mingw/bin:/bin:/c/Program Files (x86)/MiKTeX 2.8/miktex/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/MATLAB/R2010a/runtime/win64:/c/Program Files/MATLAB/R2010a/bin:/c/Program Files (x86)/MKVtoolnix I'm guessing /usr/local/bin is /bin, and mingw/bin is set by the postinstall script to wherever you have a mingw compiler installed Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should always be before MSYS's bindir, and that . will certainly cause trouble with GCC's build system. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
2010/6/15 JonY jo...@users.sourceforge.net On 6/15/2010 20:30, Ruben Van Boxem wrote: 2010/6/15 JonYjo...@users.sourceforge.net On 6/15/2010 19:31, Ruben Van Boxem wrote: I didn't have such issues cross compiling GMP in Cygwin or Linux. Well, MSYS is special :s (see other thread on my link.exe removal). MSYS is not special at all to configure scripts. How does your PATH look? I am very puzzled how this can happen. I know this, I meant the precautions and gotcha's MSYS sometimes has, like the link.exe issue we are having here. My PATH from within MSYS is this: .:/usr/local/bin:/mingw/bin:/bin:/c/Program Files (x86)/MiKTeX 2.8/miktex/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/MATLAB/R2010a/runtime/win64:/c/Program Files/MATLAB/R2010a/bin:/c/Program Files (x86)/MKVtoolnix I'm guessing /usr/local/bin is /bin, and mingw/bin is set by the postinstall script to wherever you have a mingw compiler installed Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should always be before MSYS's bindir, and that . will certainly cause trouble with GCC's build system. That's exactly why I said MSYS is special... and I don't know what will break if I try to fix it. I still find it very odd that GMP configure even knows about the name link, because no mingw toolchain even has such a thing. Shouldn't the script use ld or something else for its tests? -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 6/15/2010 21:49, Ruben Van Boxem wrote: Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should always be before MSYS's bindir, and that . will certainly cause trouble with GCC's build system. That's exactly why I said MSYS is special... and I don't know what will break if I try to fix it. I still find it very odd that GMP configure even knows about the name link, because no mingw toolchain even has such a thing. Shouldn't the script use ld or something else for its tests? IIRC MSYS post installs sets mingw/bin before MSYS bins, not after, and there was never a . in my MSYS, never a good idea on anything resembling UNIX. Are you sure its a vanilla install? -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
2010/6/15 JonY jo...@users.sourceforge.net On 6/15/2010 21:49, Ruben Van Boxem wrote: Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should always be before MSYS's bindir, and that . will certainly cause trouble with GCC's build system. That's exactly why I said MSYS is special... and I don't know what will break if I try to fix it. I still find it very odd that GMP configure even knows about the name link, because no mingw toolchain even has such a thing. Shouldn't the script use ld or something else for its tests? IIRC MSYS post installs sets mingw/bin before MSYS bins, not after, and there was never a . in my MSYS, never a good idea on anything resembling UNIX. Are you sure its a vanilla install? I downloaded all MSYS packages, extracted them to the same dir, and double-clicked msys.bat. Then I did sh /postinstall/pi.sh and y y m:/development/mingw64. It was pleased to not find make and said everything was set up. But: path *order* is okay, /usr/local/bin points to /local/bin and is empty (until you put something in there yourself), then /mingw/bin, then /bin, so mingw/bin is before MSYS bin. The . comes from the /etc/profile file, which explicitely prepends this to the rest of the path on line 19/21. I just noticed Earnie's justification: # My decision to add a . to the PATH and as the first item in the path list # is to mimick the Win32 method of finding executables. This still has nothing to do with the configure script even looking for a link command IMHO. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 6/16/2010 01:37, Ruben Van Boxem wrote: 2010/6/15 JonYjo...@users.sourceforge.net On 6/15/2010 21:49, Ruben Van Boxem wrote: Hmm, I think /mingw/bin or where your mingw-w64 toolchain bindir is should always be before MSYS's bindir, and that . will certainly cause trouble with GCC's build system. That's exactly why I said MSYS is special... and I don't know what will break if I try to fix it. I still find it very odd that GMP configure even knows about the name link, because no mingw toolchain even has such a thing. Shouldn't the script use ld or something else for its tests? IIRC MSYS post installs sets mingw/bin before MSYS bins, not after, and there was never a . in my MSYS, never a good idea on anything resembling UNIX. Are you sure its a vanilla install? I downloaded all MSYS packages, extracted them to the same dir, and double-clicked msys.bat. Then I did sh /postinstall/pi.sh and y y m:/development/mingw64. It was pleased to not find make and said everything was set up. But: path *order* is okay, /usr/local/bin points to /local/bin and is empty (until you put something in there yourself), then /mingw/bin, then /bin, so mingw/bin is before MSYS bin. The . comes from the /etc/profile file, which explicitely prepends this to the rest of the path on line 19/21. I just noticed Earnie's justification: # My decision to add a . to the PATH and as the first item in the path list # is to mimick the Win32 method of finding executables. This still has nothing to do with the configure script even looking for a link command IMHO. OK, but I still cannot understand how it can fail. That . in PATH is a recipe for failure especially if you want to build GCC. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
On 6/10/2010 01:41, Chris Saunders wrote: I think that I installed MSYS correctly for my Windows 7 64-bit system. I downloaded and attempted to run configure on GMP-5.0.1 and got some output that made me think I have a problem: $ ./configure --disable-shared --enable-alloca=no checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 In the post-install part I set the location to the directory where I extracted the 64-bit version of MinGW(on my computer it is C:\MinGW_64). What made me wonder is that I am seeing i686-pc-mingw32 and think that I should be seeing 64 at the end of this. I'm wondering if I likely did something wrong or should I expect to see this? you forgot to set --build and --host, msys usually means mingw.org gcc, which you are not trying to use. you need to set host to x86_64-w64-mingw32. Build can stay i686-pc-mingw32. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Installing MSYS to use mingw-w64
I think that I installed MSYS correctly for my Windows 7 64-bit system. I downloaded and attempted to run configure on GMP-5.0.1 and got some output that made me think I have a problem: $ ./configure --disable-shared --enable-alloca=no checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 In the post-install part I set the location to the directory where I extracted the 64-bit version of MinGW(on my computer it is C:\MinGW_64). What made me wonder is that I am seeing i686-pc-mingw32 and think that I should be seeing 64 at the end of this. I'm wondering if I likely did something wrong or should I expect to see this? Regards Chris Saunders From: Ruben Van Boxem Sent: Wednesday, June 09, 2010 10:28 AM To: mingw-w64-public@lists.sourceforge.net Subject: Re: [Mingw-w64-public] Installing MSYS to use mingw-w64 Lets hope this mail end up in the right thread... You can download a complete MSYS package (with every binary provided by mingw.org) so that you don't have to bother figuring out which of them you need. It's the MSYS-date.zip (not the *-src-* one!) package located here. This is one package containing all the original binaries of MSYS as distributed by mingw.org. This provides only unix tools (coreutils, ssh, sftp, sed , etc...), no compiler. You will have to download that seperately. If you want to build 32-bit applications, there are automated and personal builds here. If you want to build 64-bit applications, there are automated and personal builds here. You'll want the latest one ending in *-mingw_date. They are regularly updated, and it's best to keep up to date as much as possible, as there is continuous bug fixing going on. For the personal builds, there is a *-x86_64-mingw-date package which means the toolchain is 64-bit itself and you will need to be running a x64 OS. The automated builds don't have a x64 one. The personal builds by sezero also have gmake/mingw32-make included, which is required to build most projects. To install: 1) unzip MSYS anywhere, say C:\msys so that bash.exe is located in C:\msys\bin. 2) unzip the mingw-w64/w32 toolchain anywhere, say C:\mingw64 so that gcc.exe (or *-gcc.exe) is located in C:\mingw64\bin 3) doubleclick or create a shortcut to C:\msys\msys.bat. Running this will open a bash shell. 4) Like the readme says, first thing you should do is run the following command: sh /postinstall/pi.sh Answer y, y, location of mingw64 or mingw32 folder, here it's C:/mingw64 5) Do what you need to do :) I will get a wiki page up for this soon. If you need any more help feel free to ask! -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Installing MSYS to use mingw-w64
I have been unsuccessful at getting MSYS to work with MinGW-w64. I also have had problems getting the latest version of MSYS - there seems to be a lot of files and I don't know what needs to be downloaded. Could anyone assist? My OS is Windows 7 64-bit. Regards Chris Saunders-- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
