Closed cculianu closed 7 months ago
The new release is 3.11.3, not 3.11.2.
Hmm... you're right. I was just on latest master which appears to be tagged v3.11.2. I just did git checkout v3.11.3
and did a build and it works now. My bad. Seems to be fixed on v3.11.3
. Closing.
PS: Why not have master be.. you know.. like the latest release? Why all these crazy branches? What's the value in that? I never understand why some projects do these things... anyway.. sorry for the false report.
This is my bad: the latest release has not yet been merged to master.
This is my bad: the latest release has not yet been merged to master.
Done.
Description
I'm on macOS with macports. Latest master (which happens to be v3.11.2 release tag). I did:
I get tons of errors and warnings. Ditto when I try and use g++-13 or clang++-17 on macOS. Build always fails with various warnings and errors. See attached example errors.
Reproduction steps
Expected vs. actual results
Expected it to build and not fail.
Note that on the
develop
branch things work so idk maybe this is a dupe of a previous bug. Still.. considering you just did a release I would have expected stuff to work and not fail?Minimal code example
No response
Error messages