GCC 4.1.1 for MinGW

[Ceniza]

For those interested in trying the latest release of GCC, I'll be providing a link to GCC 4.1.1 for MinGW in my signature in a few minutes.

GCC 4.1.0 was able to compile Code::Blocks but failed compiling wxWidgets. GCC 4.0.3 was able to compile wxWidgets but failed compiling Code::Blocks. I wonder how it'll be for GCC 4.1.1 (I'm gonna try soon)

That said, wait for the link

[Ceniza]

Too bad... this version failed to compile wxWidgets 2.6.3

Anyway, the link is there if anyone feels like trying it.

[yaoye]

Too bad... this version failed to compile wxWidgets 2.6.3

Anyway, the link is there if anyone feels like trying it.

nice work, thank you!

[killerbot]

thx.

Ceniza,
did you ever discuss this with the wx people ??


Cheers,
Lieven

[Michael]

Too bad... this version failed to compile wxWidgets 2.6.3

Good work. Another GCC version to try out .

Did you try to compile C::B with it?

Best wishes,
Michael

[Michael]

did you ever discuss this with the wx people ??

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]

nice work, thank you!

np

did you ever discuss this with the wx people ??

Well, I'd say the real problem is GCC itself, but every single bug I've reported has been marked as duplicated

Did you try to compile C::B with it?

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]

Did you try to compile C::B with it?

Nop. When I saw it failed compiling wx just like 4.1.0 did, I restored 3.4.5 immediately and went to sleep

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.

[siomek]

Right, it was downloader problem. Thanks for help.

[jarro_2783]

why do newer versions of gcc fail to compile lots of things anyway?

[Ceniza]

why do newer versions of gcc fail to compile lots of things anyway?

Well, the new versions of GCC include many changes and many new optimization features, and just as one would expect, such a big project with such big changes can lead to some evil bugs.

What's sad is the win32 port seems to be the most buggy one

[Someone]

why do newer versions of gcc fail to compile lots of things anyway?

Well, the new versions of GCC include many changes and many new optimization features, and just as one would expect, such a big project with such big changes can lead to some evil bugs.

What's sad is the win32 port seems to be the most buggy one

Thanks a lot for the compilation.
So far, works for me - fine.
I did compile fltk2 and gsl :-)
The only think is that the code is normally a bit ~30kb bigger that the code compiled with gcc (mingw) 3.4.5.
It would be very interest to see if the situation will change with compilation options a bit altered.
Could you please, before rebuilding gcc replace all "-g -o2" and "-o2" instances on "-Os -fno-exceptions -DHAVE_INLINE". This instructions known to drastically reduce size of executables (hence libraries).

[jarro_2783]

so it's not that there has been a change in the way c++ works, it's that such a huge upgrade of something like a compiler is bound to cause bugs?