Ryan Carsten Schmidt

Looking at the web site again, I see now that there is also a link at the bottom that reads "jp2a on DarwinPorts". That too needs to be changed to...

Looks like I had already submitted a pull request to fix some of these issues in https://github.com/cslarsen/csl.name/pull/1 I've now submitted a new pull request to fix the remaining issues in...

We at MacPorts are also [still waiting](https://trac.macports.org/ticket/57863) for a new working release or at least a git tag of the working 1.0.6 version.

> Ok guys, I seriously need help with this 😆 I can at least tag 1.0.6, but which commit ID do you want? Whichever commit was used to produce to...

In the mean time, you could suggest to Homebrew that they downgrade jp2a to 1.0.6. Or you're welcome to come over to MacPorts where [we have jp2a 1.0.6](https://ports.macports.org/port/jp2a).

Is this it? https://github.com/Bushmills/Bashforth

Thanks. I've updated [bashforth in MacPorts](https://ports.macports.org/port/bashforth/summary) to this version. (The web page won't reflect this update until later today.) You may want to make the new home of bashforth more...

Whoops, that's a typo I made when updating the port. Thanks for pointing it out.

How would git determine what "the proper version tags" are? I am not building in a git clone. And I am not configuring with `-DC4CORE_DEV=ON`.

> ``` > #error "unknown standard library" > ``` It looks like this happens when `_LIBCPP_ABI_NAMESPACE` is not defined: https://github.com/biojppm/c4core/blob/e55d82c6acaec7509841cb5ad115d3fcd5c01d9a/src/c4/std/vector_fwd.hpp#L27-L35 It looks like `_LIBCPP_ABI_NAMESPACE` was introducd in https://github.com/llvm/llvm-project/commit/fe13c13cc236aebe042b58f1e7fa9f6712e037b9 which first...