-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails with clang on macOS < 13: Undefined symbols for architecture x86_64: "std::__1::to_chars(char*, char*, double)"
#973
Comments
It seems like it's not supporting |
I see. I did set the requirement for C++20 https://github.com/macports/macports-ports/blob/bacd5a9fb13699ba325c954f929e898a2a4098e2/net/parabolic/Portfile#L42 which in theory is supposed to ensure the correct compiler gets picked, but possibly it did not work quite right here (does P. S. On a side note, are you interested to be a maintainer for |
According to this: https://stackoverflow.com/a/71778011 it should work with As far as being a maintainer, sure I guess, but I don't own/use any macOS system. I plan on trying to create a macOS VM on my Linux machine tho. |
Any update on this? |
It appears that it needs Xcode 15.3+: https://developer.apple.com/xcode/cpp The standard may support it, but Apple There is some chance it would work via This is not your bug, so no need to delay any updates. There is no requirement to support any older macOS versions, it is done as long as it is possible and maintainer is willing to. We may be willing, but it may not be possible here :) Could I have your e-mail handle, to use for the portfile’s maintainer field? |
BTW let me close the issue, since it is Apple’s bug, not |
Parabolic
is in MacPorts now, and turns out linking stage fails for macOS < 13.Complete log: https://build.macports.org/builders/ports-12_x86_64-builder/builds/123779/steps/install-port/logs/stdio
Any idea what goes wrong?
P. S. On 10.6 I use gcc with libstdc++, there no errors. Also on macOS 13+ with Apple clang it works fine.
The text was updated successfully, but these errors were encountered: