User forums > General (but related to Code::Blocks)
TDM's unofficial GCC 4.2.0 for MinGW (now with OpenMP, Fortran and Obj-C)
TDragon:
There are some strange things going on here -- fortunately, I'm now able to reproduce the problem. One note before I start looking for a good solution: the "nonexistent directory" messages are to be expected, because GCC is running on a system other than the one it was compiled on. Unfortunately the "-v" option doesn't show what's happening during the relative-to-self search which, for Windows systems, is supposed to (and usually does) turn up the correct location to find the file. I can speculate that the problem is directly tied to a lack of awareness of Windows' "current volume" concept.
dwmcqueen:
Well, it also fails if you don't use MinGW as your directory. I needed to revert to the earlier one, since I use C:\MinGW-4.2
dwmcqueen:
That is true. Two seconds to rename, two seconds to rename back, and so on. However, if the compiler needs to be in non-standard I:\MingW then that is okay. Really no reason for me to have that old compiler on there anyways - is there?
Why are we on a death wish wanting to use our own folder names for the compiler?? That I do not understand.
I think the problem is the earlier release did not have this issue, and could be located wherever. People get used to things when they work, and then don't like them when something changes that changes the whole schematic.
TD has done wonderful work. I just didn't expect to have to install his package in one location and one location only.
TDragon:
--- Quote from: dwmcqueen on July 03, 2007, 06:14:46 pm ---I think the problem is the earlier release did not have this issue, and could be located wherever. People get used to things when they work, and then don't like them when something changes that changes the whole schematic.
TD has done wonderful work. I just didn't expect to have to install his package in one location and one location only.
--- End quote ---
That is in fact one of my primary goals when creating these releases: to achieve the same amount of flexibility of location as the official MinGW packages. As far as I'm concerned, you should be able to install it in C:\MinGW or Q:\ZarkingFrood as you please. :)
So I've been digging to find out how exactly this is accomplished. My 4.1.2 builds all succeed in this, but only the first 4.2.0 build did, and it was crossed-native-compiled from Ubuntu Linux. So I'm going to go ahead and create a third and hopefully final 4.2.0 release, which will include the same optimizations I used for the second, but will be cross-native-compiled as the first one.
Keep your eyes peeled for it!
-John E. / TDM
Edit:
It's now here -- gcc-4.2.0-tdm-3: optimized but fully relocatable; install wherever you like! There should also be no more unnecessary accesses of your CD drives, etc. I have also made a build supporting OpenMP parallelization through the "-fopenmp" option.
madd:
Is support for 64 bit included in these binaries?
Also it seems to use STL from v3.4.5.
I.e. if I rename includes/c++/3.4.5 to something else it wont compile programs that use STL, unless I manually add 4.2.0 to the include dirs..
Am I the only one with this problem?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version