-
Notifications
You must be signed in to change notification settings - Fork 114
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
Botan needlessly disabled on macOS #52
Comments
@randombit thanks for opening an issue! I've tried to re-enable botan on mac-os in PR #53 but it causes a CI failure.
Do you know how it can be fixed? |
@est31 Interesting - I just added a macOS CI build for the Rust wrapper in randombit/botan-rs#38 and everything worked fine but I see you are using a vendored build and that may make a difference somehow. Possibly on macOS we should be using Clang's |
Oh I found out what is going on - our vendored build needs to be able to dynamically link against the system C++ library and that code was written to always use |
@randombit thanks for digging up the cause! Please ping me if you make the release! |
|
Vendored botan 0.8.1 works fine on macos now. Thanks to the botan author for finding the cause of the build failure. Closes #52
Huh apparently the PR hit an ICE in nightly Rust: rust-lang/rust#83126 ... it only happens on mac OS, that's strange. |
Vendored botan 0.8.1 works fine on macos now. Thanks to the botan author for finding the cause of the build failure. Closes #52
Vendored botan 0.8.1 works fine on macos now. Thanks to the botan author for finding the cause of the build failure. Closes #52
Just an FYI the logic in #42 is incorrect, Botan supports macOS (aka
x86_64-apple-darwin
) just fine, and has for years. It does not support the old MacOS "Classic" which nobody uses anymore. I think the confusion came about because of the recent rebranding of OS X to macOS, plus the fact that the docs even bothered mentioning Classic, which has been dead for 20 years. I've amended Botan's documentation so the situation is more clear.The text was updated successfully, but these errors were encountered: