User forums > General (but related to Code::Blocks)

TDM-GCC 4.8 series (Latest: 4.8.1-tdm-2 - 2013-10-06)

(1/9) > >>

TDragon:
I've released new packages that should fix the drive-not-present errors, as well as the LTO error. No fix yet for the DW2 EXE-to-DLL exception bug.


For those of you who have patiently waited more than a year since the previous TDM-GCC release, your wait is over. I'm pleased to present:

TDM-GCC 4.8.1
This release includes out-of-the-box DLL-free std::thread support, 64-bit Ada support, and the usual slew of GCC improvements.

TDM-GCC 4.8.1, the first TDM release in the GCC 4.8 series, is now available for download. As always, I've tested it on wxWidgets (2.8.12) and Code::Blocks SVN (9368) to ensure good compatibility. You can build Code::Blocks with either the TDM32 edition ("out of the box"), or the TDM64 edition (using the MinGW-w64 project's runtime and the "-m32" flag for 32-bit compilation). When building wxWidgets as a MONOLITHIC DLL, you will probably need to use the "-fno-keep-inline-dllexport" flag (mingw32-make ... CXXFLAGS="-fno-keep-inline-dllexport").

Some TDM-specific changes since the last release:

* TDM-GCC now uses POSIX-style threads in its runtime libraries by way of the MinGW-w64 "winpthreads" layer. This allows std::thread and other C++11 pthreads-based features to be used.
* TDM-GCC's version of winpthreads is patched for fully static use, so you won't be distributing an additional pthreads DLL with your programs. The patch gives winpthreads the ability to share thread handles among DLLs and EXEs.
* By popular request, the "-static-libstdc++" option is back. It doesn't do anything, because TDM-GCC uses a static libstdc++ by default and you have to use "-shared-libstdc++" to get the DLL version, but it doesn't cause a compile-time error anymore.
* By dint of some upstream work and some TDM-GCC-specific hacking, the Ada language is finally available for the TDM64 edition (32-bit or 64-bit compilation).
TDM-GCC comes in TWO editions:
You can choose between the classic TDM 32-bit edition and the TDM64 edition. The TDM64 edition is based on the MinGW-w64 runtime API and the x86_64-w64-mingw32 GCC target, and can create both 32-bit and 64-bit code, with the "-m32"/"-m64" compiler flags. Please be aware, if you build Code::Blocks yourself, that it only works as 32-bit code ("-m32") on Windows, currently -- though that will hopefully change soon. Also, please never mix 32-bit object files (.o), libraries (.a), DLLs, or EXEs with 64-bit versions, and don't report it as a bug if you inadvertently do.

More information and downloads are available at <http://tdm-gcc.tdragon.net/>. TDM-GCC includes support for C, C++, Fortran, Objective-C/C++, and Ada, as well as support for the OpenMP multithreading extensions, packaged in a simple Windows installer.

Disclaimer:
As always, please remember:

* TDM-GCC is not formally affiliated with or endorsed by the MinGW project.
* No level of support for TDM-GCC is in any way guaranteed (although a best effort is made to fix bugs as they are found or forward them to GCC Bugzilla).
Cheers,
John E. / TDM

ollydbg:
Hi, John, thank you for the good work, I'm going to try your 32 bit dw2 edition now.

BTW, I just create a windows batch script to name all the *-dw2.exe files (strip the -dw2), hope that is useful for someone.

--- Code: ---Setlocal EnableDelayedExpansion
for /f  %%i in ('dir /b *-dw2.exe') do (
set name=%%i
set name=!name:-dw2=!
ren %%i !name!
)

--- End code ---

MortenMacFly:

--- Quote from: TDragon on September 29, 2013, 12:36:18 am ---For those of you who have patiently waited ...

--- End quote ---
That includes me then... ;-)

Its always like x-mas if I read posts like this. Thank you once again, John!

...and nice new webpage design, btw...

gd_on:
Thanks,
nevertheless I have a problem that I don't understand :
When I simply launch CB I obtain error messages like this one (here translated from French) :
mingw32-gcc.exe - No disk
There are no disk in the drive. Insert a disk in \Device\Harddisk4\DR4

and

x86_64-w64-mingw32-gcc.exe - No disk
There are no disk in the drive. Insert a disk in \Device\Harddisk4\DR4

If I load a project and try to compile it, I obtain the same messages at each mingw32 call.
If I click on ignore the message, the project is compiled correctly, but it becomes annoying when you have a big project with many calls to mingw32 (CB for example !).

What could be the problem ?

If I revert to 4.71 version, all is OK again.

gd_on

TDragon:
Hi gd_on,

Can you see if it's possible to add the "-v" option to your command line and show me the output? I'd just like to see the command line output of compiling *one* file with that option, when it produces these error screens for you.

Navigation

[0] Message Index

[#] Next page