Same problem here.
Configuration: Windows 8.1, with 8.1 SDK, and visual studio 2013.
I tried to link manually phobos64 with no success. Anyway there
is the windows page saying that WinMain automatically forces the
compiler to link phobos.
What is even more strange is that if you take
Has a bug report been filled? Or any news regarding this issue?
By the way I'm using VisualD, going to check now if I get the
same problem with command line.
On Saturday, 9 November 2013 at 16:46:36 UTC, evilrat wrote:
On Saturday, 9 November 2013 at 16:22:07 UTC, deed wrote:
phobos64.lib contains
_D4core7runtime7Runtime10initializeFDFC6object9ThrowableZvZb
but not
_D4core7runtime7Runtime10initializeFZb
Does this mean that the phobos64.lib is not aligned with
current core.runtime module?
i also have this problem on win 8.1 with visual studio 2013.
smells like a bug for me. file a bug on tracker.
for now i think manually calling rt_init() and rt_term() can be
used to avoid it.
