MinGW Release. D2.058 x86-64

[Dmitry Olshansky]

On 27.04.2012 7:19, Daniel Green wrote:
> Please post all issues in D.gnu or on GDC's site
> https://bitbucket.org/goshawk/gdc
>
> Due to the use of a newer runtime than TDM64-GCC it is **recommended**
> to install a copy specifically for GDC.
>
> Features
> **ALPHA** As in, D2.058 support is still new.
> * D2.058
> * Debug information available using gnu-debuglink.
> * Removed D1(Did anyone use this featuer?).
> * Due to current system breaking with repository changes and D1
> being discontinued at the end of the year.
> * binutils with TLS patches
> * mingw-w64-runtime with TLS and stdio fixes.
> * GCC 4.6.1 with TLS patches
>
> Installation instructions:
>
> 1. Download and install TDM MinGW64
> 2. Extract the downloaded archive into the base of the newly installed
> TDM install.
>
> If you've done this before, you can just do step 2.
>
> MinGW64 installer
> http://tdm-gcc.tdragon.net/
>
> GDC binary
> https://bitbucket.org/goshawk/gdc/downloads/gcc-4.6.1-tdm64-1-gdc-7e1a98da2769-20120426-D2.058.7z
>
>
> Known issues:
> * May break TDM64 C++.
> * Field-less structs will throw a null this exception. When formatted by
> std.format. runnable/test23.d

Decided to play with GDC a bit. Strange.
I get :
C:\Users\Demon\AppData\Local\Temp\ccs8AWDr.o:fred_r.d:(.text+0x2789): 
undefined reference to `_Dmodule_ref'
C:\Users\Demon\AppData\Local\Temp\ccs8AWDr.o:fred_r.d:(.text+0x279e): 
undefined reference to `_Dmodule_ref'
c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.1/../../../../lib\dmain.o: 
In function `dmain._D5dmain9__modinitFZv':
C:\crossdev\gdc64\v2\build\x86_64-w64-mingw32\libphobos\libdruntime/../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain.d:1: 
undefined reference to `_Dmodule_ref'
C:\crossdev\gdc64\v2\build\x86_64-w64-mingw32\libphobos\libdruntime/../../../../gcc-4.6.1/libphobos/libdruntime/rt/dmain.d:1: 
undefined reference to `_Dmodule_ref'

<snip> (a LOT of references to _Dmodule_ref)

Before I try to workaround this beast anyone have an idea what's wrong?

-- 
Dmitry Olshansky