On 10/30/2011 21:12, Prof Brian Ripley wrote:
> It seems this version has e.g. cc1.exe built against libstdc++6.dll.
> Why does a C-code compiler front-end need C++ support?  (The 4.6.2
> version did not, nor does any cc1 I have ever seen.)
> 

PPL is still required for graphite afaik, its C++, but gcc uses cloog to
use it.

> The issue is that you can normally run the 32-bit compiler as
> 
> /path/to/mingw32/bin/gcc
> 
> and the 64-bit one as
> 
> /path/to/mingw64/bin/gcc
> 
> but not in this build (and cc1.exe etc are also linked against the
> libwinpthread-1.dll).  This provides a simple and transparent way to
> build both 32- and 64-bit versions of applications without forever
> manipulating paths.
> 

Did you happen to rename the prefixed versions?

You could have the prefixed versions working nicely without playing with
PATHS, or having both of them called "gcc".

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to