-
Notifications
You must be signed in to change notification settings - Fork 572
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
[Libevent] Rebuild for new platforms #10489
Conversation
I assume you know how to build against OpenSSL these days; it requires special sauce... Look at |
The rsync build seems to filter out windows saying that we are unable to link openssl. Should we wait until then? Otherwise, we would add some platforms and lose some. Ah and we don't have openssl on riscv in any case. So this won't get us much anyways. |
If you want to build against
The
in the beginning of the build script. The reason for these shenanigans is that the OpenSSL version number wasn't updated to 3.0.16 as we're doing for all other packages. |
Seems like it all went through. I wish I hadn't merged the tmux. Presumably, tmux can just be retriggered to pick up everything since it already has the new JLLWrappers etc. |
Not without changing version number if it needs changing compat bounds (I haven't checked) |
I just merged tmux earlier today (with a new version number), so I think it should have picked up all the new compat bounds. The new one should probably just pick up riscv binaries. |
Does this look good to merge - especially the openssl stuff? |
The PR looks good. I haven't looked at the build output, especially for riscv64 and aarch64-freebsd, to see whether there are important warnings. |
No description provided.