On 5/1/2012 1:53 AM, Iain Buclaw wrote:
> no _Dmodule_ref would probably mean no object_.d was compiled in.

In D2.058, the _Dmodule_ref code was moved to minfo.d.  I didn't properly move the GNU specific stuff on the first build, problem didn't surface until I compiled it with MinGW.

They reduced it to OSX, Posix for including _Dmodule_ref.  Which is why linux didn't exhibit the same problems.

I added it back but there's a chance the 32-bit library wasn't updated properly.

On 1 May 2012 17:31, Daniel Green <venix1@gmail.com> wrote:

> On 5/1/2012 1:53 AM, Iain Buclaw wrote:
>
>> no _Dmodule_ref would probably mean no object_.d was compiled in.
>>
>
> In D2.058, the _Dmodule_ref code was moved to minfo.d.  I didn't properly move the GNU specific stuff on the first build, problem didn't surface until I compiled it with MinGW.
>
> They reduced it to OSX, Posix for including _Dmodule_ref.  Which is why linux didn't exhibit the same problems.
>
> I added it back but there's a chance the 32-bit library wasn't updated properly.
>

No problem, I only depend on x64 for the time being, so it's no problem to use that :)