Issues with undefined symbols when using Vibe on Windows

[Jonathan M Davis]

On Monday, July 02, 2018 18:26:27 Chris M. via Digitalmars-d-learn wrote:
> On Monday, 2 July 2018 at 17:33:20 UTC, Bauss wrote:
> > On Monday, 2 July 2018 at 12:53:19 UTC, Chris M. wrote:
> >> On Friday, 29 June 2018 at 20:08:49 UTC, Chris M. wrote:
> >>> On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote:
> >>>> On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
> >>>>> [...]
> >>>>
> >>>> Are you compiling to 64bit?
> >>>>
> >>>> Else the functions will be named GetClassLongA and
> >>>> SetClassLongA
> >>>
> >>> Yeah, that's what I'm targeting
> >>>
> >>>> Vibe builds fine on 64bit for me and I think that's
> >>>> outdated. It hasn't been modified for 4 years.
> >>>
> >>> Seems to be an issue when I import vibe.core.concurrency
> >>
> >> Bumping this one back up
> >
> > If I don't get around it tonight then I will tomorrow and see
> > if I can find a solution for you or perhaps figure out what
> > exactly goes wrong.
> >
> > Kinda half important for me too to fix something like this
> > since I have a framework relying on vibe.d
>
> Thanks for checking, I have no idea what else to try (short of
> getting MS Build Tools somehow, but I unfortunately can't in my
> current environment so I'm stuck with DMC + DMD)

How are you compiling for 64-bit without the MS toolchain?

- Jonathan M Davis