Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: kylove on March 03, 2008, 09:38:31 am

Title: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: kylove on March 03, 2008, 09:38:31 am
CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: thomas on March 03, 2008, 12:35:11 pm
Nothing prevents you from using the tech preview version of MinGW.
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: asdz on March 03, 2008, 01:15:25 pm
CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
is there a gcc 4.2.* version supported on Windows?
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: thomas on March 03, 2008, 01:54:00 pm
Yes, but it is considered a "technology preview" release.
For the most part, it works nicely from what I can tell (using it every day), but it requires a few initial tweaks during setup, and it may have issues that are not yet known.

Considering that some of our users still don't know the difference between a poll and a normal thread, we did not deem it a good idea to bundle a "non-stable" compiler as the default.
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: JGM on March 03, 2008, 02:12:14 pm
Considering that some of our users still don't know the difference between a poll and a normal thread, we did not deem it a good idea to bundle a "non-stable" compiler as the default.

That was a good one  :lol:
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: asdz on March 15, 2008, 04:22:09 pm
could someone help me how to download a GCC 4.2 compiler version or greater, for using it on windows with code blocks?
Mingw has only 3.4 version...i would like 4.2 version or later.....
thank you in advance
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: thomas on March 15, 2008, 04:31:25 pm
Well, download the 4.2.1 version from the MinGW download site, what is preventing you from doing that? It's not like it's rocket science :)
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: asdz on March 15, 2008, 06:15:40 pm
Well, download the 4.2.1 version from the MinGW download site, what is preventing you from doing that? It's not like it's rocket science :)
maybe smthg i am doing wrong.... i am browsing Mingw site and the only release i can see is MinGW-5.1.3
I run it and there isn't GCC version 4.2.1...
It can only install GCC 3.4....
Could you help me find out what is my mistake?
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: anwender4711 on March 15, 2008, 06:37:31 pm
look here (http://sourceforge.net/project/showfiles.php?group_id=2435)
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: asdz on March 15, 2008, 07:29:14 pm
look here (http://sourceforge.net/project/showfiles.php?group_id=2435)
this is the page where i d/led MingW...
Couldn't find what we are talking about....
GCC 4.2.1 version i see is only for linux distr...
Sorry about my annoying questions....
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: anwender4711 on March 15, 2008, 07:37:22 pm
GCC 4.2.1 version i see is only for linux distr...
Don't get confused by the tar.gz archives. They are containing windows binaries.
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: asdz on March 16, 2008, 05:12:39 pm
thanx a million guys!
i found it out!
one more last problem...
Can't compile with Openmp... any hints on that?
Title: Re: CodeBlocks why not used MinGW 5.x (gcc 4.2.x) version
Post by: Ceniza on March 16, 2008, 07:09:32 pm
thanx a million guys!
i found it out!
one more last problem...
Can't compile with Openmp... any hints on that?

It seems the OpenMP library that comes with MinGW 4.2.1 depends on PThreads, which is not included. There's a PThreads implementation for Win32 from the redhat guys at http://sources.redhat.com/pthreads-win32/index.html

You are free to experiment with it, but don't expect us to help you any further. It just doesn't belong here.