On 08.09.2012 22:00, Luis Lavena wrote:
> Hello,
>
> I'm starting to use GCC 4.7.1 (win32 threading model) on both win32
> and win64 OS and noticed the executables are no longer prefixed.
>
> Previous builds had the executables prefixed, which I was instructured
> were result of cross-compiled compilers and not native ones.
>
Yes, and no.
A cross compiler will be prefixed, but a compiler created by a cross
compiler would /probably/ be not prefixed.
To create a cross compiler with GCC you must compile it with something
like this: --build=x86_64-unknown-linux-gnu
--target=powerpc-unknown-linux-gnu --host=x86_64-unknown-linux-gnu.
That cross compiler will be named powerpc-unknown-linux-gnu-gcc. The
configure line means that the compiler will be built on a
x86_64-unknown-linux-gnu, will run on a x86_64-unknown-linux-gnu, but
will produce binaries that run on powerpc-unknown-linux-gnu.
Now, if you want to create a native powerpc compiler with the cross
compiler you must use something like this:
--build=x86_64-unknown-linux-gnu --target=powerpc-unknown-linux-gnu
--host=powerpc-unknown-linux-gnu. And do it at little bit more
interestning: --build=x86_64-unknown-linux-gnu
--target=sparc-unknown-linux-gnu --host=powerpc-unknown-linux-gnu. That
will compile a compiler that is built on x86_64, will run on a powerpc
and produce binaries that will run on a sparc.
A normal installation of GCC will create both gcc and
x86_64-unknown-linux-gcc (dependent on your triplet)
--
chs
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
