I can't move forward with my extern(C++) work until we do something
about the build issues.

I'm waiting/blocked on these patches: https://github.com/dlang/druntime/pull/2442 https://github.com/dlang/druntime/pull/2446 https://github.com/dlang/druntime/pull/2444

There appears to be one OSX build machine that fails due to an old
build environment (as I'm told).
Who are the people that have access to these machines?

std::array, and std::string_view can't be tested because the C++ toolchains are too old (don't all support C++11/14/17).

The toolchains are all out of date, and it's throwing up issues constantly. How do we resolve this?

On Tuesday, 8 January 2019 at 03:33:29 UTC, Manu wrote:
> I can't move forward with my extern(C++) work until we do something
> about the build issues.
>
> I'm waiting/blocked on these patches: https://github.com/dlang/druntime/pull/2442 https://github.com/dlang/druntime/pull/2446 https://github.com/dlang/druntime/pull/2444
>
> There appears to be one OSX build machine that fails due to an old
> build environment (as I'm told).
> Who are the people that have access to these machines?
>
> std::array, and std::string_view can't be tested because the C++ toolchains are too old (don't all support C++11/14/17).
>
> The toolchains are all out of date, and it's throwing up issues constantly. How do we resolve this?

As noted elsewhere, 2446 builds fine when -g is removed. 2442 and 2444 are both green, are they good to go?

On Mon, Jan 7, 2019 at 7:40 PM Nicholas Wilson via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>
> As noted elsewhere, 2446 builds fine when -g is removed. 2442 and 2444 are both green, are they good to go?

#2442 is good to merge, and the follow-up PR can continue the debate
in the feed.
#2444 and #2446 are building with your patch... if that goes green,
they they're good.