User forums > General (but related to Code::Blocks)
GCC 4.1.1 for MinGW
Michael:
--- Quote from: killerbot on May 28, 2006, 10:08:49 am ---did you ever discuss this with the wx people ??
--- End quote ---
Hello,
I have spoken a lot, but concerning GCC 4.1.0. There should be at least one thread in this forum.
To make it short :), I could compile wxWidgets (Patch 2), but not linking it :(.
Unfortunately, no solution until now (AFAIK).
Best wishes,
Michael
Ceniza:
--- Quote from: yaoye ---nice work, thank you!
--- End quote ---
np :)
--- Quote from: killerbot ---did you ever discuss this with the wx people ??
--- End quote ---
Well, I'd say the real problem is GCC itself, but every single bug I've reported has been marked as duplicated :)
--- Quote from: Michael ---Did you try to compile C::B with it?
--- End quote ---
Nop. When I saw it failed compiling wx just like 4.1.0 did, I restored 3.4.5 immediately and went to sleep :)
Michael:
--- Quote from: Ceniza on May 28, 2006, 04:51:11 pm ---
--- Quote from: Michael ---Did you try to compile C::B with it?
--- End quote ---
Nop. When I saw it failed compiling wx just like 4.1.0 did, I restored 3.4.5 immediately and went to sleep :)
--- End quote ---
Ok :).
Personally, I use wxWidgets 2.6.3 (+Patch 2) built with GCC 4.0.3 for building C::B with GCC 4.1.0 (later with your newest GCC 4.1.1 version) :).
Best wishes,
Michael
siomek:
GCC 4.1.1 - MINGW.7z is not supported archive. The same for all gcc versions from site. Windows xp sp2, 7-zip 4.42.
Ceniza:
Some download managers seem to have problems getting files from there and they get corrupted. A way to check if your download is fine is to run md5sum on it (a quick search in Google for md5sum.exe should be enough to get it) and compare the hash value you get with that provided in the site (the .md5 file).
If the hash value is different then your file is corrupted, but if it's the same then your "unpacker" has problems.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version