GCC 4.2.1 binary release for mingw is available from MINGW

[stahta01]

https://sourceforge.net/project/showfiles.php?group_id=2435&package_id=241304

Direct link to notes
http://internap.dl.sourceforge.net/sourceforge/mingw/gcc-4.2.1-dw-release_notes.txt

GCC 4.2.1 binary release for mingw is available.

You can download it from:
https://sourceforge.net/project/showfiles.php?group_id=2435

The binaries are archived by language.

There are two versions, differing in the model used for exception unwind info.
  (1) Setjump-longjump (sjlj).  Historically,and currenetly, the default model.
  (2) Dwarf2 table-based unwinding (dw2).  The more efficient model.


*This is built with Dwarf 2 unwind info enabled. The gcc, g++ and
gfortran drivers in the bin directory have a '-dw2' suffix to indicate
that, You can remove '-dw2; from these files if you like.

If you want sjlj you will find them (soon) in the gcc-4.2.1-sjlj-1 package

The binaries were compiled with --enable-version-specific-runtime-libs.
The runtime libs are in <mingw-root>/lib/gcc/mingw32/gcc-4.2.1-dw2. Do
not move these files. If you really must, don't bother reporting
installation bugs.

Tim S

[dwmcqueen]

You beat me to it.  I hope (and think) that TDragon's builds had some impact.  We had been batting those away on the MinGW list earlier....

[killerbot]

allright, this weekend I will try to build CB with it on windows. In case all seems fine, I might kick out a nightly with this. Could it be, at last, bye bye GCC 3.4.x ;-)

[stahta01]

allright, this weekend I will try to build CB with it on windows. In case all seems fine, I might kick out a nightly with this. Could it be, at last, bye bye GCC 3.4.x ;-)

I am getting errors like below for wxWidgets and Code::Blocks, the error below is wxWidgets 2.9 trunk. Going to try another installation with different binutils.

Code

C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/ccNY169T.s: Assembler messages:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/ccNY169T.s:1448: Error: invalid character '_' in mnemonic
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/ccNY169T.s:1465: Warning: .def pseudo-op used inside of .def/.endef: ignored.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/ccNY169T.s:1465: Error: junk at end of line, first unrecognized character is `_'
mingw32-make: *** [gcc_mswuddll\monodll_archive.o] Error 1

Error building wxWidgets reported by someone else on below link.

http://article.gmane.org/gmane.comp.gnu.mingw.user/23362

[roland]

I was able to successfully build Allegro 4.2.2 and all of its components and demo programs with this version, but am unable to build it with TDM's latest build of 4.2.1.

Here is my post on the issue:  http://forums.codeblocks.org/index.php/topic,6512.msg50658.html#msg50658

So, all in all, a good sign, I think.

[TDragon]

Awesome! Seems like it's about time for my builds to take the back seat again.

Edit:
If we get that bug fixed. Yup, it's there in 2.8.4 too.

[thomas]

allright, this weekend I will try to build CB with it on windows. In case all seems fine, I might kick out a nightly with this. Could it be, at last, bye bye GCC 3.4.x ;-)

Tried already, would have been too good if it worked.

First, the wxWidgets headers gernerate a thousand warnings (which is not so severe), and then it fails with
{standard input}:14784: Error: invalid character '_' in mnemonic
{standard input}:14801: Warning: .def pseudo-op used inside of .def/.endef: ignored.
{standard input}:14801: Error: junk at end of line, first unrecognized character is `_'

...whatever it means. No hint as to what source file the error refers to.

[patlecat]

Wow finally they did it. But TD can you tell us what took them so long? And when can we expect the next full MingW release?

And what about wxWidgets 2.9? Does anyone know how far this is? And what it will contain?

[MortenMacFly]

BTW: If you use the MinGW installer you will get mingw-runtime-3.13.tar.gz instead of mingw-runtime-3.12.tar.gz which is officially announced. Might be that this is related... or not... don't know as I'm ill and have to stay in bed.
With regards, Morten.

[Biplab]

BTW: If you use the MinGW installer you will get mingw-runtime-3.13.tar.gz instead of mingw-runtime-3.12.tar.gz which is officially announced. Might be that this is related... or not... don't know as I'm ill and have to stay in bed.

mingw-runtime-3.13 and win32-api-3.10 has been released couple of days back. They are someway related to the latest gcc release.

Get well soon.

[stahta01]

BTW: If you use the MinGW installer you will get mingw-runtime-3.13.tar.gz instead of mingw-runtime-3.12.tar.gz which is officially announced. Might be that this is related... or not... don't know as I'm ill and have to stay in bed.

mingw-runtime-3.13 and win32-api-3.10 has been released couple of days back. They are someway related to the latest gcc release.

Get well soon.

From http://internap.dl.sourceforge.net/sourceforge/mingw/gcc-4.2.1-dw-release_notes.txt

* libstdc++ and libgfortran require version 3.13 of mingw-runtime and
  w32api version 2.2 or higher.

* This package does _not_ contain binutils, the mingw-runtime
  or the w32api. You will need to get these if you do not already
  have mingw installed.

* libstdc++ and libgfortran require version 3.13 of mingw-runtime and
  w32api version 2.2 or higher.  Yes, I've said it twice now.

* Static and dll libraries of libgcc and libstdc++ are in the release.
  By default, linkage is to static libraries.  More details later.

* OpenMP is enabled.  To use it you will need to have  win32-pthreads package
  installed. More details later.

[wxLearner]

* Static and dll libraries of libgcc and libstdc++ are in the release.
  By default, linkage is to static libraries.  More details later.

Has anybody found a shared version (dll) of libgcc?

[stahta01]

* Static and dll libraries of libgcc and libstdc++ are in the release.
  By default, linkage is to static libraries.  More details later.

Has anybody found a shared version (dll) of libgcc?

No, I do have libstdc++ DLL and mingwm10.dll

Tim S

[dwmcqueen]

First, the wxWidgets headers gernerate a thousand warnings (which is not so severe), and then it fails with
{standard input}:14784: Error: invalid character '_' in mnemonic
{standard input}:14801: Warning: .def pseudo-op used inside of .def/.endef: ignored.
{standard input}:14801: Error: junk at end of line, first unrecognized character is `_'

...whatever it means. No hint as to what source file the error refers to.

According to the MinGW list - they are aware of the problem and will issue an update shortly.  Apparently they were too aggressive with some 4.3.0 backports.

[dwmcqueen]

Wow finally they did it. But TD can you tell us what took them so long? And when can we expect the next full MingW release?

I can tell you - they were ready to issue the binaries, but not ready to support the release since they were still too busy on the prior release.  Someone stepped in and offered to help support the release - so they released it.