-
Notifications
You must be signed in to change notification settings - Fork 13
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
Crate fails to build in github actions on version macOS 12.6.5 #8
Comments
Since this is a recurring theme, perhaps its best to approach this with conditional compilation. What do you think? |
Sorry for being dense, but I'm not sure I am following what you are suggesting. Are you saying add feature flags to the crate for these functions allowong opt out to avoid compiling? |
Not at all, totally legitimate question. My bad for not being thorough. I'm referring specifically to this. More than a feature flag, it is a way to have a specific piece of code compile only on certain conditions. It uses the exact same mechanism as features. |
@lweberk maybe. I think it has more to do the openssl/libxml version installed on mac os x and for that reason wouldn't want to go with an OS level target. This has been compiling flawlessly for years on github actions, and on my older mac it still does as well. Thus, doing an OS target seems a bit too heavy of a hammer... |
I see. You have a point there. There is also the case of multiple libs being shipped on the same platform with different sets of support for the different crypto algorithm families. So its a highly moving target. That makes me think back to you mentioning feature flags. Have feature flags for the different crypto algo families. In this case I can see MacOS is shipping openssl without MD5 and its variants. Which can be seen as a very sensible thing to do. Perhaps a flag for all MD5, as well as the AES-CBC which are already out commented due to Ubuntu incompatibilities. And so on and so forth... Currently I'm totally swamped, will have a deeper look at it during the weekend. |
@lweberk perhaps moving to https://github.com/RustCrypto would help? |
@itsbalamurali No, unfortunately not. Since we are wrapping libxmlsec, it in turn having its own notion of its backend for sourcing its crypto primitives |
I'm experiencing this same issue on my MacBook Pro, Apple M1 Max, Version 15.1.1. Any chance a fix is available? |
@Will5 I'm building on Github Actions OSX with my fork. I don't have a mac to test with.
It however fails to sign xml for me. Maybe you can help with it, I don't have a mac, so its hard for me to move this further: |
As an FYI this crate no longer builds on github actions
runs-on: macos-latest
I'm sort of waiting for the next image update to see if it is still broken, but thought I'd report this in case anyone else has the issue later.
openssl = { version = "0.10", features = ["vendored"] }
[xmlsec = "0.2.2"]
Failure is on
Last time it successfully built was on:
Current errors:
The text was updated successfully, but these errors were encountered: