Ryan Carsten Schmidt
Ryan Carsten Schmidt
What advantage is there for the user in being able to disable these features? In other words, why do we need variants?
Previous discussion about adding a startup item is at https://trac.macports.org/ticket/67736
Duplicate of #2053.
I've updated the pure ports to indicate that they don't support arm64 natively. That should allow you to install the port on your arm64 system and receive the x86_64 version,...
> Is that the only incompatibility? No; you can search the build log for `error:` to see other unknown identifiers being used, which possibly also have older names that could...
Using a new compiler like clang 20 reveals more problems: ``` configure:7331: checking if signal handlers must be reinstalled when invoked configure:7385: ccache /opt/local/bin/clang-mp-20 -o conftest -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch...
> Isn't this fixed in current HEAD? I don't know. I'm sure a lot has changed in the nearly five years since 3.5.99.22 was released. That's the latest version I...
I tested the latest commit on the 3.6.x branch, 58d42b6edf3b08c34878448ca0153cede91463cf, and the problem is still there.
> The system header must be relatively new, which is why it worked fine previously, but fails now. Compilers that support C++20 and later have this header. According to [MacPorts...
> According to [MacPorts research](https://trac.macports.org/wiki/CompilerSelection#LanguageStandards) this is clang 16 and later from llvm.org and clang 1500 and later from Apple Xcode 15 and later. But evidently some earlier versions also...