Re: [Mingw-w64-public] [Project News | New Builds]
I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? On Sun, Nov 2, 2014 at 10:42 AM, niXman i.nix...@autistici.org wrote: *ANNOUNCING* GCC-4.9.2 builds are released. Program *versions* in builds: 1. *GCC-4.9.2* 2. *binutils-2.24* 3. *mingw-w64 v3 git c6f0d3d981c70ad31bb1c2bfc2850b827281e189* 4. *gdb-7.8.1* 5. *python-2.7.8(with dev-files)* 6. *make-4.1* Links: 32-bit: posix-sjlj: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/sjlj/i686-4.9.2-release-posix-sjlj-rt_v3-rev0.7z posix-dwarf: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/dwarf/i686-4.9.2-release-posix-dwarf-rt_v3-rev0.7z win32-sjlj: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-win32/sjlj/i686-4.9.2-release-win32-sjlj-rt_v3-rev0.7z win32-dwarf: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-win32/dwarf/i686-4.9.2-release-win32-dwarf-rt_v3-rev0.7z 64-bit: posix-sjlj: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/sjlj/x86_64-4.9.2-release-posix-sjlj-rt_v3-rev0.7z posix-seh: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/seh/x86_64-4.9.2-release-posix-seh-rt_v3-rev0.7z win32-sjlj: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/sjlj/x86_64-4.9.2-release-win32-sjlj-rt_v3-rev0.7z win32-seh: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/seh/x86_64-4.9.2-release-win32-seh-rt_v3-rev0.7z The online installer is also available: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe -- Regards, niXman ___ Dual-target(32 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___ Another online IDE: http://liveworkspace.org/ -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Project News | New Builds]
2014-11-03 10:30 GMT+01:00 Baruch Burstein bmburst...@gmail.com: I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? Because this is a native toolchain. Native toolchains don't have everything prefixed. Your makefile shouldn't be using any prefixes, and just call the bare gcc etc. instead. Cheers, Ruben -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Project News | New Builds]
On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2014-11-03 10:30 GMT+01:00 Baruch Burstein bmburst...@gmail.com: I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? Because this is a native toolchain. Native toolchains don't have everything prefixed. Your makefile shouldn't be using any prefixes, and just call the bare gcc etc. instead. a. Then why are some prefixed? b. Is there another way to determine in the makefile if compiling for x64 or x32 without using the compiler executable name? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Project News | New Builds]
2014-11-03 16:45 GMT+01:00 Baruch Burstein bmburst...@gmail.com: On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2014-11-03 10:30 GMT+01:00 Baruch Burstein bmburst...@gmail.com: I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? Because this is a native toolchain. Native toolchains don't have everything prefixed. Your makefile shouldn't be using any prefixes, and just call the bare gcc etc. instead. a. Then why are some prefixed? That's the whole GCC/binutils/autotools ecosystem that does that and uses that. Don't ask me for the reasons, I did not write the tools way back when. b. Is there another way to determine in the makefile if compiling for x64 or x32 without using the compiler executable name? First, a makefile shouldn't care if it's building for 32 or 64-bit. That is a distinction you'd want to make at the code-level, if you need to make it at all. If you want to be able to cross-compile, a good way is to have the makefile accept an option like CROSS_PREFIX, which could be i686-w64-mingw32-, and passed in like: make CROSS_PREFIX=i686-w64-mingw32- And prefixing all calls to the tools with this prefix. For native toolchains, just make with an empty CROSS_PREFIX would work. Cheers, Ruben -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Project News | New Builds]
From: bmburst...@gmail.com Date: Mon, 3 Nov 2014 17:45:59 +0200 To: mingw-w64-public@lists.sourceforge.net Subject: Re: [Mingw-w64-public] [Project News | New Builds] On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem vanboxem.ru...@gmail.commailto:vanboxem.ru...@gmail.com wrote: 2014-11-03 10:30 GMT+01:00 Baruch Burstein bmburst...@gmail.commailto:bmburst...@gmail.com: I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? Because this is a native toolchain. Native toolchains don't have everything prefixed. Your makefile shouldn't be using any prefixes, and just call the bare gcc etc. instead. a. Then why are some prefixed? It's the specification of gcc. b. Is there another way to determine in the makefile if compiling for x64 or x32 without using the compiler executable name? Determine by checking size of void* in configure. If you don't want to use configure, just add shell variables setting in your Makefile (for example, ARCH=x86_64 make ...) -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Project News | New Builds]
On Mon, Nov 3, 2014 at 3:45 PM, Baruch Burstein bmburst...@gmail.com wrote: On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2014-11-03 10:30 GMT+01:00 Baruch Burstein bmburst...@gmail.com: I am curious why only a few of the executables get prefixed versions? I just tried running a certain makefile with prefixed versions of the toolchain, and it failed looking for the prefixed versions of 'ar' and 'windres'. Easily solvable (make a copy and prefix it), but I am still curious why some get it by default while others don't? Because this is a native toolchain. Native toolchains don't have everything prefixed. Your makefile shouldn't be using any prefixes, and just call the bare gcc etc. instead. a. Then why are some prefixed? b. Is there another way to determine in the makefile if compiling for x64 or x32 without using the compiler executable name? To be pedantic, you'll never be running x32 on Windows: http://en.wikipedia.org/wiki/X32_ABI -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
