On 3/20/08, Arthur Norman <[EMAIL PROTECTED]> wrote: > ... since everybody is very active today! > > I run on Vista-x86_64, and run under a cygwin shell so I have all the > 32-bit development tools I like. When I compile I go "-mno-cygwin" and > that is how my scripts and autoconf things are all set up. > > With mingw-w64-bin-x86_64-mingw_20080320.tar.bz2 unpacked and its bin > dircetory put on the front of my path I have two things that cause me pain > (and yes I can cope). (a) it provides binaries with names such as gcc and > g++ because it thinks it is native - which it is - but those then shadow > the regular 32-bit cygwin ones I have, and until -m32/-m64 bi-arch is > there I would feel happier if the binaries remained named as for cross > compilation. Also if they did it would be easier to just switrch paths and
For (a), just use the cygwin cross compiler. It should blend very nicely with your cygwin environment, and it will have all of the prefixed filenames. The gcc executable itself will be a 32-bit cygwin-linked exe running under WoW, whereas the gcc that you downloaded is a native 64-bit exe linked only to the MSVCRT. However, if what you want is a cross compiler, you can use the cross compiler. If you are building the toolchain yourself, you can achieve a native toolchain with cross-compiled-esque prefixes with a configure option (something like --program-transform-name or some such switch). ------------------------------------------------------------------------- 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 Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
