User forums > General (but related to Code::Blocks)
TDM's unofficial GCC 4.2.0 for MinGW (now with OpenMP, Fortran and Obj-C)
nenin:
Now looks like OK!
TDragon:
madd:
Nope, sorry. I'm not sure what the state of 64-bit support in MinGW is at the moment, actually. *Makes a mental note to look at the recent win64 releases*
For the problem with using the wrong STL: it seems like an older driver or other older file is being used incorrectly. You should probably try reinstalling from a "clean slate" -- i.e. install all your desired MinGW packages (except gcc-core and gcc-g++), and then install mine.
20-40:
It's hard to answer everything you've brought up (in fact it's hard to read and understand most of your posts in the first place), but in a general way I disagree with you. I do not provide a "crippled" compiler, nor am I aware that I have in any way "nullified" any "configure procedures" that would otherwise have worked with a distribution of GCC which used hard-coded paths for a single installation directory. One of my foremost aims as a software engineer is to provide software that "just works" -- so, if you can show me how the software I distribute fails to "just work" for a common scenario, I will try my hardest to correct it. Finally, I believe it's safe to say that in fact this is a compiler which needs nothing more than its "bin" directory in Windows' PATH.
Cheers,
John E. / TDM
dwmcqueen:
Well, thanks again!
BTW, what bugs have you encountered with latest WinAPI and binutils?
TDragon:
For kicks and giggles, and so everyone can see that flexibility of GCC's installation isn't a pie-in-the-sky dream, I installed MinGW's packages and mine in "C:\MinGW GCC in a path\with spaces", made sure that the only MinGW-related environment variable was "C:\MinGW GCC in a path\with spaces\bin" tacked onto the end of PATH, made sure that no directories named "mingw" or "MinGW" existed anywhere (or any of the directory names used when compiling on Ubuntu), and built wxWidgets 2.8.4 and Code::Blocks, both on drive G:\, completely without a hitch. That's what I call freedom, folks.
--- Quote from: dwmcqueen on July 04, 2007, 08:33:38 pm ---BTW, what bugs have you encountered with latest WinAPI and binutils?
--- End quote ---
The latest binutils' "windres" has a bug that shows up while building wxWidgets; it was mentioned on a MinGW mailing list and Danny Smith (I believe) had a fix for it that should appear in the next MinGW binutils release.
As far as the latest w32api package goes, I don't remember for sure when and how I encountered the bug, though I think it, also, occured while using or building wxWidgets. Since you asked, I'll see if I can track it down again.
Later edit:
I didn't encounter any bugs building with the latest version, so it may have been a bug in 3.8 that got ironed out in 3.9. I'll have to update my docs. Thanks for reminding me.
Cheers,
John E. / TDM
blahhh:
TDM. The sources for GCC 4.2.0 are patched according to your site:
http://www.tdragon.net/recentgcc/
Why and what did you patch? The GCC 4.2 release compiles out of the box when I download it from gcc.gnu.org. I'm building a mingw compiler using a cygwin environment (hence it's not a cross compiler or something, I just like cygwin's environment more than msys).
I'm wandering what you are patching and also why it takes so long for MinGW to release an official Gcc 4 cause I see no bugs at all.
Thnx, blahhh
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version